RFC7959 - blockwise for error responses? #25
Comments
|
On Tue, Sep 06, 2022 at 06:05:13AM -0700, Achim Kraus wrote:
The resulting question will be, if it's not possible, to have a blockwise error-response, what is then considered to be the payload in that proxy use-case?
I agree that blockwise on error responses is just not possible.
The best suggestion I can give is to turn the HTTP 4xx response into
problem-details document (RFC-to-be 9290), and return that on a
successful 2.05 Content code. I'm not sure though how that'd be best
distringuished from a genuine HTTP 200 OK document of the same data (for
a general-purpose proxy), and whether it needs to be distinguished from
that in the first place.
|
|
The data in a HTTP 404 response in my experience is used to give some clues (with marginal benefit, but looks pretty) as to why the server had to generate a 404 error, but is really down to the page is not available. Thus, dropping the data provided in the HTTP response is no great loss from my point of view. However, if the CoAP is going to be converted back to html in a downstream proxy it would be nice to have some basic html in the 4.04 CoAP response body that is used to state the obvious. So, perhaps on converting from html to CoAP instead of dropping all the html that is too large, a simple piece of basic html is used instead otherwise the downstream proxy will need some smarts to build a 404 response page - which is unlikely. |
|
Thanks both for your feedback. |
See core-wg/corrclar#25 Signed-off-by: Achim Kraus <achim.kraus@cloudcoap.net>
See core-wg/corrclar#25 Signed-off-by: Achim Kraus <achim.kraus@cloudcoap.net>
I currently hit a "very special case".
A coap2http proxy receives an http error (404) and a page with about 2k.
If the 404 is translated into 4.04, "my stack" (Eclipse/Californum) refuses to do that as blockwise transfer.
So, are error responses considered to be transferred with blockwise with block2?
I didn't found something in RFC7959, but maybe I overseen it.
The text was updated successfully, but these errors were encountered: