<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 20 Jan 2016, at 8:56 AM, Robert Collins <<a href="mailto:robertc@robertcollins.net" class="">robertc@robertcollins.net</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class=""><blockquote type="cite" style="font-family: Helvetica; font-size: 16px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">REQUEST_URI environ variable<br class="">~~~~~~~~~~~~~~~~~~~~~~~~~~~~<br class=""><br class="">Multiple contributors expressed an interest in bringing this environment variable into WSGI directly, making it a required part of the environ dictionary. An alternative name for this was RAW_URI.<br class=""></blockquote><br style="font-family: Helvetica; font-size: 16px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><span style="font-family: Helvetica; font-size: 16px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">If its reasonable available to e.g. Apache modules, I could see doing</span><br style="font-family: Helvetica; font-size: 16px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><span style="font-family: Helvetica; font-size: 16px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">this. That said, why have two? Why not require that URI be the 'RAW'</span><br style="font-family: Helvetica; font-size: 16px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><span style="font-family: Helvetica; font-size: 16px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">URI? I don't see the benefit in having two separate variables.</span></div></div></blockquote></div><br class=""><div class="">The history on this one was that Apache and anything that copied what Apache did always provided this as REQUEST_URI. It has some de-facto standing therefore as meant it was also always present in many CGI, SCGI, FASTCGI environments as a result.</div><div class=""><br class=""></div><div class="">When Gunicorn decided to add the equivalent, they chose not to use what Apache has always used and chose a different name.</div><div class=""><br class=""></div><div class="">It isn’t an issue therefore of allowing both, it makes more sense only to note use of REQUEST_URI as it has longer standing. If adopted, Gunicorn would need to use REQUEST_URI, but only Gunicorn would have to continue to use RAW_URI to support people who wrote WSGI applications which were only looking for what Gunicorn used and didn’t know there was another convention for it.</div><div class=""><br class=""></div><div class="">As to the comment:</div><div class=""><br class=""></div><div class=""> Why not require that URI be the ‘RAW’ URI?</div><div class=""><br class=""></div><div class="">am not sure what you ‘UR’ you are talking about, if you are talking about some other existing variables in the WSGI specification.</div><div class=""><br class=""></div><div class="">Graham</div></body></html>