-
Notifications
You must be signed in to change notification settings - Fork 101
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
Progress doesn't work if X-Progress-ID is set with more headers module #10
Comments
Can you attach (or send me privately by e-mail) the full debug log (you'll need to compile nginx with --with-debug)? |
I've mailed it to you. |
I also checked debug log and as you suggest get_tracking_id is called earlier then headers are set. How can I fix it? |
1 similar comment
I also checked debug log and as you suggest get_tracking_id is called earlier then headers are set. How can I fix it? |
Hmm, reading more headers documentation, it looks like "more_set_headers" sets output headers (the one that will be returned to the client). |
Yep, that solve half of problem. But first call get_tracking_id is performed earlier then setting of headers. In our application we need to proxy traffic to Amazon that reject requests with querystring. So currently we have solve problem in following way. We receive querystring param. Set header using querystring value and then remove querystring with rewriting.
|
Do you mean the problem is solved by the rewrite break? |
Rewrite required to remove "/upload". set $args "" removes "X-Progress-ID" from querystring. |
In our application we need X-Progress-ID to be parsed from $request_url
location /upload {
if ($request_uri ~* ^/upload/(.*)$) {
set $progress_id $1;
more_set_headers "X-Progress-ID:$progress_id";
}
proxy_pass http://127.0.0.1;
proxy_redirect default;
track_uploads proxied 30s;
}
However progress doesn't work in this case.
The text was updated successfully, but these errors were encountered: