We have a filesystem product with an edit method that allows users to change some properties. At the end, the user is redirected to the page from which they came. Our setup has Squid in front on port 80, with Pound on port 81 load-balancing to 3 ZEO clients. No matter how we define the redirect URL - even when we hardcoded it explicitly with ':80' for test purposes - the redirection is always to port 81. What is going on? Thanks! Ken ____________________________________________________________________________________ Looking for earth-friendly autos? Browse Top Cars by "Green Rating" at Yahoo! Autos' Green Center. http://autos.yahoo.com/green_center/
--On 25. Mai 2007 01:26:32 -0700 Ken Ara <feedreader@yahoo.com> wrote:
We have a filesystem product with an edit method that allows users to change some properties. At the end, the user is redirected to the page from which they came.
Our setup has Squid in front on port 80, with Pound on port 81 load-balancing to 3 ZEO clients.
No matter how we define the redirect URL - even when we hardcoded it explicitly with ':80' for test purposes - the redirection is always to port 81. What is going on?
Improper virtualhosting configuration? Without a detailed description it is unlikely that someone might help. -aj
Virtual hosting for us is limited to two lines in the default VHM mappings: mysite.org/mysite *.mysite.org/mysite This minimal arrangement has worked for several years, although Pound and ZEO are new for us. No other problems. Ken --- Andrew Milton <akm@theinternet.com.au> wrote:
+-------[ Ken Ara ]---------------------- | We have a filesystem product with an edit method that | allows users to change some properties. At the end, | the user is redirected to the page from which they | came. | | Our setup has Squid in front on port 80, with Pound on | port 81 load-balancing to 3 ZEO clients. | | No matter how we define the redirect URL - even when | we hardcoded it explicitly with ':80' for test | purposes - the redirection is always to port 81. What | is going on?
Your rewrite rule (if any), is not traversing through your Virtual Host Monster correctly.
-- Andrew Milton akm@theinternet.com.au
--- Andreas Jung <lists@zopyx.com> wrote:
Improper virtualhosting configuration? Without a detailed description it is unlikely that someone might help.
-aj
____________________________________________________________________________________ Park yourself in front of a world of choices in alternative vehicles. Visit the Yahoo! Auto Green Center. http://autos.yahoo.com/green_center/
+-------[ Ken Ara ]---------------------- | Virtual hosting for us is limited to two lines in the | default VHM mappings: | | mysite.org/mysite | *.mysite.org/mysite | | This minimal arrangement has worked for several years, | although Pound and ZEO are new for us. No other | problems. Right, but, when you 'forward' from pound or squid into Zope, you need to reference your Zope portion via the Virtual Host Monster, in order to have the <baseref> tags that Zope generates be correct. e.g. http://127.0.0.1:8080/VirtualHostBase/http/mysite.org:80/mysite/VirtualHostR...... -- Andrew Milton akm@theinternet.com.au
Thanks for bringing this up! I have always wanted to know: since the introduction of VHM I have never used this 'VirtualHostBase' business. I have only ever used the mappings tab as mentioned below; no Apache or other redirect rules. All has always worked perfectly. Am I finally being bitten by this? BTW, I always override the <baseref> tags. Ken --- Andrew Milton <akm@theinternet.com.au> wrote:
+-------[ Ken Ara ]---------------------- | Virtual hosting for us is limited to two lines in the | default VHM mappings: | | mysite.org/mysite | *.mysite.org/mysite | | This minimal arrangement has worked for several years, | although Pound and ZEO are new for us. No other | problems.
Right, but, when you 'forward' from pound or squid into Zope, you need to reference your Zope portion via the Virtual Host Monster, in order to have the <baseref> tags that Zope generates be correct.
e.g.
http://127.0.0.1:8080/VirtualHostBase/http/mysite.org:80/mysite/VirtualHostR......
-- Andrew Milton akm@theinternet.com.au
____________________________________________________________________________________ Moody friends. Drama queens. Your life? Nope! - their life, your story. Play Sims Stories at Yahoo! Games. http://sims.yahoo.com/
+-------[ Ken Ara ]---------------------- | Thanks for bringing this up! I have always wanted to | know: since the introduction of VHM I have never used | this 'VirtualHostBase' business. I have only ever used | the mappings tab as mentioned below; no Apache or | other redirect rules. All has always worked perfectly. | Am I finally being bitten by this? I would say so. | BTW, I always override the <baseref> tags. That's obviously not working for you in this case. -- Andrew Milton akm@theinternet.com.au
Thanks for that. Well, I don't feel like changing everything just because of this one new feature (user editing). Instead, could I add something in my edit method, ahead of return REQUEST.RESPONSE.redirect(redir_url()) to inform Zope about the port to use? Ken --- Andrew Milton <akm@theinternet.com.au> wrote:
+-------[ Ken Ara ]---------------------- | Thanks for bringing this up! I have always wanted to | know: since the introduction of VHM I have never used | this 'VirtualHostBase' business. I have only ever used | the mappings tab as mentioned below; no Apache or | other redirect rules. All has always worked perfectly. | Am I finally being bitten by this?
I would say so.
| BTW, I always override the <baseref> tags.
That's obviously not working for you in this case.
-- Andrew Milton akm@theinternet.com.au
____________________________________________________________________________________Need a vacation? Get great deals to amazing places on Yahoo! Travel. http://travel.yahoo.com/
Hello, Please allow me to ask this question again, because there is still an unsolved mystery.
--On 25. Mai 2007 01:26:32 -0700 Ken Ara <feedreader@yahoo.com> wrote:
We have a filesystem product with an edit method that allows users to change some properties. At the end, the user is redirected to the page from which they came.
Our setup has Squid in front on port 80, with Pound on port 81 load-balancing to 3 ZEO clients.
No matter how we define the redirect URL - even when we hardcoded it explicitly with ':80' for test purposes - the redirection is always to port 81. What is going on?
For us, virtual hosting is limited to two lines in the VHM 'mappings' tab: oursite.org/oursite *oursite.org/oursite Way back when VHM was new I tried skipping the part about 'VirtualHostBase'. The instructions under 'About' were a bit cryptic: the statement, "VHM doesn't do anything unless it sees one of the following special path elements in a URL: VirtualHostBase sets the protocol and host, while VirtualHostRoot sets the path root" seemed inaccurate - for me, everything just worked. All I had to do was override the <baseref> tag and avoid the use of absolute_url (or just remove ':81'). But I digress. The weird thing is, before moving to our present server, we had Squid on port 80 and Zope on port 81 with the same VHM setup (same ZODB). We never had any problem with redirection. So I doubt this VHM aspect really plays a role in our problem. Actually, Pound is the only new element apart from the change from Zope 2.7 to 2.10. As a workaround, would there be something I could add when calling RESPONSE.redirect to force the redirect to port 80? Thanks again Ken ____________________________________________________________________________________You snooze, you lose. Get messages ASAP with AutoCheck in the all-new Yahoo! Mail Beta. http://advision.webevents.yahoo.com/mailbeta/newmail_html.html
+-------[ Ken Ara ]---------------------- | We have a filesystem product with an edit method that | allows users to change some properties. At the end, | the user is redirected to the page from which they | came. | | Our setup has Squid in front on port 80, with Pound on | port 81 load-balancing to 3 ZEO clients. | | No matter how we define the redirect URL - even when | we hardcoded it explicitly with ':80' for test | purposes - the redirection is always to port 81. What | is going on? Your rewrite rule (if any), is not traversing through your Virtual Host Monster correctly. -- Andrew Milton akm@theinternet.com.au
participants (3)
-
Andreas Jung -
Andrew Milton -
Ken Ara