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
The http.ResponseWriter implementation says the following thing about Content-Type header (and it actually has a note about Content-Length too).
If WriteHeader has not yet been called, Write calls
WriteHeader(http.StatusOK) before writing the data. If the Header
does not contain a Content-Type line, Write adds a Content-Type set
to the result of passing the initial 512 bytes of written data to
DetectContentType. Additionally, if the total size of all written
data is under a few KB and there are no Flush calls, the
Content-Length header is added automatically.
As of right now the lambdaurl.Wrap implementation completely misses this . . .
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is.
Following #508,
which get closed as a part of https://github.com/aws/aws-lambda-go/releases/tag/v1.42.0
However a quick search of
Content-Length
in the change log ofv1.41.0...v1.42.0
did not get any hits:
Are the Content-Length headers being added now?
Describe the solution you'd like
Add the Content-Length headers, properly.
Additional context
For a handler like:
I was able to get return from it if I try it locally, However, if using lambdaurl, I got empty returns, i.e.,
Content-Length: 0
.Please double-check. Thanks
The text was updated successfully, but these errors were encountered: