You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When sending a Response with the Flash server, and the user provides a Content-Length header, the Flash server will add an additional Content-Length header with the content length as it calculated it, where as if the Content-Length is provided to the "native" stable server, it does not duplicate the header (I am not sure if it is overriding it or if it is just letting it pass through).
It feels like the Flash server should follow the behaviour of the native stable server.
Ref: oakserver/oak#587 (I will fix it in oak by simply omitting the content-length in all cases as the servers are actually better at handling this header now)
The text was updated successfully, but these errors were encountered:
This commit changes implementation of "Deno.serve()" API to use
"Deno.serveHttp()" under the hood. This change will allow us to
remove the "flash" server implementation, bringing stability to the
"Deno.serve()" API.
"cli/tests/unit/flash_test.ts" was renamed to "serve_test.ts".
Closes#15574Closes#15504Closes#15646Closes#15909Closes#15911Closes#16828Closes#18046Closes#15869
When sending a
Response
with the Flash server, and the user provides aContent-Length
header, the Flash server will add an additionalContent-Length
header with the content length as it calculated it, where as if theContent-Length
is provided to the "native" stable server, it does not duplicate the header (I am not sure if it is overriding it or if it is just letting it pass through).It feels like the Flash server should follow the behaviour of the native stable server.
Ref: oakserver/oak#587 (I will fix it in oak by simply omitting the
content-length
in all cases as the servers are actually better at handling this header now)The text was updated successfully, but these errors were encountered: