[Web-SIG] wsgiorg.routing_args and original SCRIPT_NAME

[Ian Bicking]

Manlio Perillo wrote:
> Ian Bicking ha scritto:
>  >
>> [...]
>>
>>> 1) Do not change SCRIPT_NAME, and instead add a wsgiorg.consumed_path, a
>>>     list.
>>>
>>>     This means that the request uri recostruction must be changed:
>>>     SCRIPT_NAME = SCRIPT_NAME + '/'.join(wsgiorg.consumed_path)
>>
>> I suppose you could leave stuff on PATH_INFO.  But that doesn't seem 
>> to fit with the idea of PATH_INFO.  Also, will it be strictly 
>> SCRIPT_NAME/consumed_path/PATH_INFO, or could it be 
>> SCRIPT_NAME/consumed_path/some_other_parsing/consumed_path/PATH_INFO 
>> -- after all, there's cases where stuff gets pushed from PATH_INFO to 
>> SCRIPT_NAME, and if consumed_path is in between, which one do you push 
>> stuff to?
>>
> 
> What do you intend by some_other_parsing?

I have code that takes stuff from PATH_INFO and puts it on SCRIPT_NAME 
without updating routing_args.  It could update routing_args... but I 
guess the question still remains: if there's multiple places where this 
kind of transformation is done, which one does SCRIPT_NAME point to?

   Ian