-
-
Notifications
You must be signed in to change notification settings - Fork 363
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Response headers not being set ! #860
Comments
Could you make a fully reproducible example? I do not really believe that headers get lost that way, but I will check if I have a reproducible example. |
Sure, Dependecies:
Expected: All headers from the original request should be forwarded to the destination server.Actual: Some headers appear to be missing when the request is forwarded.
|
In case of multiple headers with the same Key(name) this works not correct, as res.set_header(...) is implemented as: This erases the previously set header of the same name. add_header(...) allows to set multiple headers withe the same name/ key, so it should correct the behavior If this solves your problem, please tell us. Then we should only correct the documentation comment and maybe the guides for set_header and add_header. BR & HTH |
I have tried that too
|
screenshot does not fit to Log output (css vs. jpeg). |
Does the raw view look different? What software is it? Can we have a tcpdump of the response? |
I get this when i use curl: When i don't touch headers:
When i use
|
Any middleware in Crow active? |
no |
I am working on a reverse-proxy server, I want to set the headers that i get after fetching the original server but it does not works. I receive 9 headers from original server but only 4 are added to current headers.
The text was updated successfully, but these errors were encountered: