Is there any progress with this issue?
I have lighttpd setup and it seems to still have the issue. Take a look at
this screenshot to see.
It's a real bummer as the NGINX has proven hard to install on centos 6.6.
At least for us. :)
On Sunday, March 1, 2015 at 10:38:37 AM UTC+2, Niphlod wrote:
>
> yep, but we do it "for the users".... in all the "important" places, like
> this, we use request.env.get('THE_PROPER_KEY')
>
> On Saturday, February 28, 2015 at 9:27:20 PM UTC+1, Massimo Di Pierro
> wrote:
>>
>> They are upper case in wsgi but we are supposed to make them all lower
>> case here:
>>
>> https://github.com/web2py/web2py/blob/master/gluon/rewrite.py#L1073
>>
>> On Saturday, 28 February 2015 10:44:35 UTC-6, Niphlod wrote:
>>>
>>>
>>>
>>> On Saturday, February 28, 2015 at 5:08:38 PM UTC+1, Massimo Di Pierro
>>> wrote:
>>>>
>>>> it is supposed to be request.env.query_string
>>>> or request.env.get('query_string'). It is supposed to be lower case and
>>>> not
>>>> upper case. If nginx has it upper case than there is a bug.
>>>>
>>>> In retrospect it was a mistake to convert all the env vars to lower
>>>> case and replace the dashed with underscore but that is what web2py does
>>>> anyway.
>>>>
>>>>>
>>>>>
>>> uhm. the problem was on lighttpd.
>>> Anyway, I think env vars are all uppercase: we just normalize them to
>>> have an underscore and be lowercase, but it's certainly not the issue at
>>> hand...web2py's code picks it up from the right place.
>>>
>>
--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list (Report Issues)
---
You received this message because you are subscribed to the Google Groups
"web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to web2py+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
