Hi Niphlod,

Thanks for response.

On Tuesday, March 26, 2013 5:14:25 PM UTC+1, Niphlod wrote:
>
> well, the underlying problem with this architecture is that on / apache 
> rewrites internally from /whatever/whatever2 to /whatever/whatever2 on the 
> default instance. From this standpoint, the default behaviour of web2py is 
> tuned "accordingly" to what apache is doing.
>
> On /dev/ apache rewrites internally /dev/whatever/whatever2 to (I suspect) 
> /whatever/whatever2 on the dev instance.
>

Correct.
 

> But, web2py doesn't know that apache has done an internal rewrite, and 
> apache doesn't rewrite outcoming urls accordingly .
>

w2p does not know this - I was using proxypassreverse to make modifications 
to the
link on the way back.
 

> Unless you play a lot with rewritecond or proxypassreverse, the better way 
> is informing web2py in advance that every /whatever/whatever2 url needs to 
> be outputted as /dev/whatever/whatever2 , so you get a consistent behaviour 
> client-side .... 
> you have to play with your routes.py on the dev instance to make it behave 
> "accordingly" to what apache is doing.
>

Hmm...this results in more differences between the dev
version and the test version than I had hoped.

There seem to be quite a few posts in various places
on how to get w2p working with apache/mod_proxy,
often via a link such as hostname/web2py - it seems
that such scenarios should have the same problem.

BR,
Seán.

 

> On Tuesday, March 26, 2013 4:41:37 PM UTC+1, Sean Murphy wrote:
>>
>> Hi,
>>
>> I'm having problems with apache config of web2py.
>>
>> I'm trying to run a test server (which others can work against)
>> and a dev server off the same apache server. Perhaps this is a
>> little crazy, but that's how we're set up now.
>>
>> From the external pov, I'm trying to configure my server such
>> that
>> hostname/ goes to the test server and
>> hostname/dev goes to the dev server
>>
>> I have the test server and the dev server installed as two
>> seperate web2py instances.
>>
>> My problem relates to the dev server and login based redirection.
>>
>> When I go to
>>
>> https://hostname/dev/admin
>>
>> I'm presented with a login form, but the send parameter on
>> the login points to /admin and not /dev/admin. More specifically,
>>
>> https://hostname/dev/admin/default/index?send=%2Fadmin%2Fdefault%2Flogin
>>
>> Hence the client tries to load hostname/admin/default/login (and not
>> the dev version) on login.
>>
>> Do I need to do anything specific with mod_proxy to catch this?
>>
>> Thanks and rgds,
>> Seán.
>>
>>
>>
>>

-- 

--- 
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 [email protected].
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to