Page MenuHomePhabricator

Use "QUERY_STRING", not "REQUEST_URI", to parse raw request parameters
ClosedPublic

Authored by epriestley on Feb 28 2019, 6:42 PM.
Tags
None
Referenced Files
Unknown Object (File)
Apr 16 2026, 10:10 AM
Unknown Object (File)
Apr 16 2026, 7:51 AM
Unknown Object (File)
Jan 31 2026, 9:16 PM
Unknown Object (File)
Jan 31 2026, 7:07 PM
Unknown Object (File)
Jan 27 2026, 1:35 AM
Unknown Object (File)
Jan 27 2026, 1:35 AM
Unknown Object (File)
Dec 11 2025, 7:07 AM
Unknown Object (File)
Dec 11 2025, 6:00 AM
Subscribers
None

Details

Summary

Fixes T13260. "QUERY_STRING" and "REQUEST_URI" are similar for our purposes here, but our nginx documentation tells you to pass "QUERY_STRING" and doesn't tell you to pass "REQUEST_URI". We also use "QUERY_STRING" in a couple of other places already, and already have a setup check for it.

Use "QUERY_STRING" instead of "REQUEST_URI".

Test Plan

Visited /oauth/google/?a=b, got redirected with parameters preserved.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable