Copyright © https://mongoose-os.com

Mongoose OS Forum

frame
ATTENTION! This forum has moved to:

https://community.mongoose-os.com

Do not post any new messages.

Authorization header blocking 304 response

For my site, Mongoose is serving HTTP requests with header including "Cache-Control: no-cache", and "If-None-Match" parameter providing the previous ETag. Usually this works correctly, and a 304 response is sent.

However, when the request includes an "Authorization" header, the 304 response is never sent, and the full document is transferred with a status 200 response. Is this correct behaviour? Perhaps it is a bug in Mongoose.

Comments

  • SergeySergey Dublin, Ireland

    To clarify, what mongoose version is that?

  • It's Mongoose 6.5.

    More details: the authentication data was actually blank, as I haven't implemented authentication yet on the client side. I'm just ignoring it. So maybe there's a parse error for the case of an empty header.

  • SergeySergey Dublin, Ireland

    Can't reproduce that with a simple curl test. Can you describe how do you observe that behavior please?

  • Thanks Sergey, I'll investigate further and give a more detailed description of the issue I'm experiencing.

Sign In or Register to comment.