Loading...

Type: Bug
Resolution: Done
Priority: Major
Fix Version/s: None
Affects Version/s: None
Component/s: None
Labels:
- 2.12-dev2
- cr-passed

Blocked:
False
Ready:
False
Discussed with Team:
No
Git Pull Request:
https://github.com/3scale/APIcast/pull/1333, https://github.com/3scale/APIcast/pull/1328
Steps to Reproduce:
Hide

Configure APIcast with:

APICAST_HTTPS_PORT

Logging policy with format similar to:

MY CUSTOM LOG: {{original_request.path}}

Run APIcast locally using the configuration attached and use the attached python script to execute https requests that reuse the same connection.
Confirm that the logs look like the attachment logs_reproduced_original_request_issue.log (the paths and hosts printed by the logging policy for each request are always those of the first request).
Show
Configure APIcast with: APICAST_HTTPS_PORT Logging policy with format similar to: MY CUSTOM LOG: {{original_request.path}} Run APIcast locally using the configuration attached and use the attached python script to execute https requests that reuse the same connection. Confirm that the logs look like the attachment logs_reproduced_original_request_issue.log (the paths and hosts printed by the logging policy for each request are always those of the first request).
Market:

Test Coverage:

+

SFDC Cases Links:
SFDC Cases Counter:
SFDC Cases Open:

When APIcast receives multiple requests on its APICAST_HTTPS_PORT from the same client in the same HTTP session, the value of the variable original_request in the liquid context will be set for the first request and will remain unchanged (wrong) for all the following requests.