Re: Wicket behind a front-end proxy
I am pretty sure my configuration is correct as per the documentation however I am having the following problem: My configuration is as follows: Apache 2.2 (mod_proxy_jk) -- Tomcat 5.5(JBoss embedded) My Wicket application filter is mapped to /* and my WAR file is deployed within a context of /web therefore URL's look like http://pabst:8080/web/mypage http://myhost:8080/web/mypage or http://pabst:8080/web/?x=TFx*mXM8oGdr1hAFT5*lkAhttp://myhost:8080/web/?x=TFx*mXM8oGdr1hAFT5*lkAetc.. using the CryptedUrlWebRequestCodingStrategy. Here is my Apache virtual host configuration for mod_proxy running on tiger proxing to pabst : VirtualHost *:80 ServerName tiger DocumentRoot /opt/www/ ProxyRequests Off Proxy * Order deny,allow Allow from all /Proxy RewriteEngine on #HACK to fix home page context issue RewriteRule ^/web(.*) $1 [R=302,NC] ProxyPass / ajp://10.0.0.1:8009/web/ ProxyPassReverse / ajp://10.0.0.1:8009/web/ ProxyPassReverseCookiePath /web / ProxyPreserveHost On RewriteLog /var/log/httpd/rewrite.log RewriteLogLevel 2 /VirtualHost This works just fine, however without the rewrite rule mentioned above the site redirects to /web/[page] under some circumstances. As far as I can tell it happens when you click on a link that requires authorization, RestartResponseAtInterceptPageException is thrown and it attempts redirect to the InterceptPage but the ProxyPassReverse rule isn't applied. It also seems to happen when ever Application.getHomePage() is called, but I can't confirm that. One last thing and I'm not sure if it matters but getHomePage() is returning a page that is an Authenticated web page, I do this because this way the URL doesn't change from the logged in home page versus the unauthenticated home page. For the people who aren't having problems with this, are you using Tomcat? Any help is appreciated. j On Dec 9, 2007 3:18 AM, Frank Bille [EMAIL PROTECTED] wrote: If you read[1], it say what you need to do (and which version of Apache httpd you need to use). Frank [1]: http://cwiki.apache.org/WICKET/wicket-behind-a-front-end-proxy.html On Dec 9, 2007 8:15 AM, sshark [EMAIL PROTECTED] wrote: Hi, I am trying the same but it does not seems to work.What I want is to be able to access Wicket application using the URL * http://www.someapps.com*instead of *http://myapps.com/wicketapps*. I am using Apache 1.3. Should I be using Apache 2.x instead? Please advise. Thanks My configuration is VirtualHost myapps.com DocumentRoot /home/vocanic/apps_vocanic_net ServerAlias www.myapps.com JkMount /* vocanic_1 /VirtualHost VirtualHost someapps.com ServerAlias www.someapps.com ProxyPass / http://localhost:10012/wicketapps ProxyPassReverse / http://localhost:10012/wicketapps #ProxyPassReverseCookiePath /citibank-survey / #not supported in Apache 1.3 /VirtualHost /lim/ p.s. I tried to post this message in reply to the topic Re: Wicket behind a front-end proxy in Nabble but it was rejected. The error was, I quoted, *This message was created automatically by mail delivery software. A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed: users@wicket.apache.org SMTP error from remote mail server after end of data: host mx1.eu.apache.org [192.87.106.230]: 552 spam score (5.0) exceeded threshold** * Can anyone shed someone light here? Thanks
Re: Wicket behind a front-end proxy
] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/Wicket-behind-a-front-end-proxy-tf4776982.html#a13821932 Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Wicket behind a front-end proxy
Hi Murat! If you are running behind a WebSeal proxy, just configure the junction as transparent and deploy your application with the same context-root as the junction name. Then you can run like: myserver1.xxx.com:80/myapp1 - localhost:8080/myapp1 The transparent setting means that the proxy will not try to parse the html and try to fix any server-relative url contained in you pages. Best Regards Niels Bo Murat Yücel-2 wrote: It seems like wicket doesnt support it, because there is no workaround on the link that Frank Bille send. There is only information about that this is a problem. /Murat 2007/11/9, Johan Compagner [EMAIL PROTECTED]: so we dont support this currently? myserver1.xxx.com:80 - localhost:8080/myapp1 myserver2.xxx.com:80 - localhost:8080/myapp2 johan On Nov 9, 2007 1:35 PM, Frank Bille [EMAIL PROTECTED] wrote: Read this again: http://cwiki.apache.org/WICKET/wicket-behind-a-front-end-proxy.html#Wicketbehindafront-endproxy-Whythisdoesn%2527talwayswork Frank On Nov 9, 2007 1:26 PM, Murat Yücel [EMAIL PROTECTED] wrote: Hi Frank I have substituted my projectname with wicket. Below is the conf for the proxy part. VirtualHost * ServerAdmin [EMAIL PROTECTED] ServerName www.wicket.com ServerAlias wicket.com ProxyRequests off ProxyPreserveHost On RewriteEngine On # Indexes + Directory Root. DirectoryIndex index.html DocumentRoot /var/wicket.com # Logfiles ErrorLog /var/log/apache2/wicket-error.log CustomLog /var/log/apache2/wicket-access.log combined ProxyPass / http://127.0.0.1:8080/wicket/ ProxyPassReverse / http://127.0.0.1:8080/wicket/ ProxyPreserveHost On /VirtualHost 2007/11/9, Frank Bille [EMAIL PROTECTED]: Sounds weird. Can you show me your apache conf for the proxy? Frank On Nov 9, 2007 12:44 PM, Murat Yücel [EMAIL PROTECTED] wrote: Hi Frank I have changed the /app/* to /* but it doesnt change the urls. They are still wrong. For example i enter the following url: www.wicket.com The url is transformed to www.wicket.com/wicket/?wicket:bookmarkablePage=%3Acom.wicket.LoginPage If i remove the the wicket part from the url then i can see the login page. But if i click on a link then the wicket part is appended again. /Murat 2007/11/9, Frank Bille [EMAIL PROTECTED]: First of all, you don't need /app/* anylonger. just /*. I'm running behind proxy as well and it works well. Are you sure you haven't run into this problem: http://cwiki.apache.org/WICKET/wicket-behind-a-front-end-proxy.html#Wicketbehindafront-endproxy-Whythisdoesn%2527talwayswork Frank On Nov 9, 2007 11:56 AM, Murat Yücel [EMAIL PROTECTED] wrote: Hi All I have looked at this article: http://cwiki.apache.org/WICKET/wicket-behind-a-front-end-proxy.html and it seems like the problem should be gone in wicket 1.3 but it isnt. I still get 404 errors. There is a warning on the wiki page: Don't use setContextPath with Wicket 1.3. I am not setting the context path. Instead i am using filter-mapping. Is this the same thing? filter-mapping filter-namewicket/filter-name !-- The app is needed for ajax (this is a known limitation/bug in wicket) -- url-pattern/app/*/url-pattern /filter-mapping Do you have a workaround for this issue or am i doing something wrong? I am currently running 1.3-beta4. Kind regards /Murat Yücel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/Wicket-behind-a-front-end-proxy-tf4776982.html#a13821932 Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e
Re: Wicket behind a front-end proxy
First of all, you don't need /app/* anylonger. just /*. I'm running behind proxy as well and it works well. Are you sure you haven't run into this problem: http://cwiki.apache.org/WICKET/wicket-behind-a-front-end-proxy.html#Wicketbehindafront-endproxy-Whythisdoesn%2527talwayswork Frank On Nov 9, 2007 11:56 AM, Murat Yücel [EMAIL PROTECTED] wrote: Hi All I have looked at this article: http://cwiki.apache.org/WICKET/wicket-behind-a-front-end-proxy.html and it seems like the problem should be gone in wicket 1.3 but it isnt. I still get 404 errors. There is a warning on the wiki page: Don't use setContextPath with Wicket 1.3. I am not setting the context path. Instead i am using filter-mapping. Is this the same thing? filter-mapping filter-namewicket/filter-name !-- The app is needed for ajax (this is a known limitation/bug in wicket) -- url-pattern/app/*/url-pattern /filter-mapping Do you have a workaround for this issue or am i doing something wrong? I am currently running 1.3-beta4. Kind regards /Murat Yücel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Wicket behind a front-end proxy
Hi Frank I have changed the /app/* to /* but it doesnt change the urls. They are still wrong. For example i enter the following url: www.wicket.com The url is transformed to www.wicket.com/wicket/?wicket:bookmarkablePage=%3Acom.wicket.LoginPage If i remove the the wicket part from the url then i can see the login page. But if i click on a link then the wicket part is appended again. /Murat 2007/11/9, Frank Bille [EMAIL PROTECTED]: First of all, you don't need /app/* anylonger. just /*. I'm running behind proxy as well and it works well. Are you sure you haven't run into this problem: http://cwiki.apache.org/WICKET/wicket-behind-a-front-end-proxy.html#Wicketbehindafront-endproxy-Whythisdoesn%2527talwayswork Frank On Nov 9, 2007 11:56 AM, Murat Yücel [EMAIL PROTECTED] wrote: Hi All I have looked at this article: http://cwiki.apache.org/WICKET/wicket-behind-a-front-end-proxy.html and it seems like the problem should be gone in wicket 1.3 but it isnt. I still get 404 errors. There is a warning on the wiki page: Don't use setContextPath with Wicket 1.3. I am not setting the context path. Instead i am using filter-mapping. Is this the same thing? filter-mapping filter-namewicket/filter-name !-- The app is needed for ajax (this is a known limitation/bug in wicket) -- url-pattern/app/*/url-pattern /filter-mapping Do you have a workaround for this issue or am i doing something wrong? I am currently running 1.3-beta4. Kind regards /Murat Yücel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Wicket behind a front-end proxy
Sounds weird. Can you show me your apache conf for the proxy? Frank On Nov 9, 2007 12:44 PM, Murat Yücel [EMAIL PROTECTED] wrote: Hi Frank I have changed the /app/* to /* but it doesnt change the urls. They are still wrong. For example i enter the following url: www.wicket.com The url is transformed to www.wicket.com/wicket/?wicket:bookmarkablePage=%3Acom.wicket.LoginPage If i remove the the wicket part from the url then i can see the login page. But if i click on a link then the wicket part is appended again. /Murat 2007/11/9, Frank Bille [EMAIL PROTECTED]: First of all, you don't need /app/* anylonger. just /*. I'm running behind proxy as well and it works well. Are you sure you haven't run into this problem: http://cwiki.apache.org/WICKET/wicket-behind-a-front-end-proxy.html#Wicketbehindafront-endproxy-Whythisdoesn%2527talwayswork Frank On Nov 9, 2007 11:56 AM, Murat Yücel [EMAIL PROTECTED] wrote: Hi All I have looked at this article: http://cwiki.apache.org/WICKET/wicket-behind-a-front-end-proxy.html and it seems like the problem should be gone in wicket 1.3 but it isnt. I still get 404 errors. There is a warning on the wiki page: Don't use setContextPath with Wicket 1.3. I am not setting the context path. Instead i am using filter-mapping. Is this the same thing? filter-mapping filter-namewicket/filter-name !-- The app is needed for ajax (this is a known limitation/bug in wicket) -- url-pattern/app/*/url-pattern /filter-mapping Do you have a workaround for this issue or am i doing something wrong? I am currently running 1.3-beta4. Kind regards /Murat Yücel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Wicket behind a front-end proxy
Hi Frank I have substituted my projectname with wicket. Below is the conf for the proxy part. VirtualHost * ServerAdmin [EMAIL PROTECTED] ServerName www.wicket.com ServerAlias wicket.com ProxyRequests off ProxyPreserveHost On RewriteEngine On # Indexes + Directory Root. DirectoryIndex index.html DocumentRoot /var/wicket.com # Logfiles ErrorLog /var/log/apache2/wicket-error.log CustomLog /var/log/apache2/wicket-access.log combined ProxyPass / http://127.0.0.1:8080/wicket/ ProxyPassReverse / http://127.0.0.1:8080/wicket/ ProxyPreserveHost On /VirtualHost 2007/11/9, Frank Bille [EMAIL PROTECTED]: Sounds weird. Can you show me your apache conf for the proxy? Frank On Nov 9, 2007 12:44 PM, Murat Yücel [EMAIL PROTECTED] wrote: Hi Frank I have changed the /app/* to /* but it doesnt change the urls. They are still wrong. For example i enter the following url: www.wicket.com The url is transformed to www.wicket.com/wicket/?wicket:bookmarkablePage=%3Acom.wicket.LoginPage If i remove the the wicket part from the url then i can see the login page. But if i click on a link then the wicket part is appended again. /Murat 2007/11/9, Frank Bille [EMAIL PROTECTED]: First of all, you don't need /app/* anylonger. just /*. I'm running behind proxy as well and it works well. Are you sure you haven't run into this problem: http://cwiki.apache.org/WICKET/wicket-behind-a-front-end-proxy.html#Wicketbehindafront-endproxy-Whythisdoesn%2527talwayswork Frank On Nov 9, 2007 11:56 AM, Murat Yücel [EMAIL PROTECTED] wrote: Hi All I have looked at this article: http://cwiki.apache.org/WICKET/wicket-behind-a-front-end-proxy.html and it seems like the problem should be gone in wicket 1.3 but it isnt. I still get 404 errors. There is a warning on the wiki page: Don't use setContextPath with Wicket 1.3. I am not setting the context path. Instead i am using filter-mapping. Is this the same thing? filter-mapping filter-namewicket/filter-name !-- The app is needed for ajax (this is a known limitation/bug in wicket) -- url-pattern/app/*/url-pattern /filter-mapping Do you have a workaround for this issue or am i doing something wrong? I am currently running 1.3-beta4. Kind regards /Murat Yücel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Wicket behind a front-end proxy
Read this again: http://cwiki.apache.org/WICKET/wicket-behind-a-front-end-proxy.html#Wicketbehindafront-endproxy-Whythisdoesn%2527talwayswork Frank On Nov 9, 2007 1:26 PM, Murat Yücel [EMAIL PROTECTED] wrote: Hi Frank I have substituted my projectname with wicket. Below is the conf for the proxy part. VirtualHost * ServerAdmin [EMAIL PROTECTED] ServerName www.wicket.com ServerAlias wicket.com ProxyRequests off ProxyPreserveHost On RewriteEngine On # Indexes + Directory Root. DirectoryIndex index.html DocumentRoot /var/wicket.com # Logfiles ErrorLog /var/log/apache2/wicket-error.log CustomLog /var/log/apache2/wicket-access.log combined ProxyPass / http://127.0.0.1:8080/wicket/ ProxyPassReverse / http://127.0.0.1:8080/wicket/ ProxyPreserveHost On /VirtualHost 2007/11/9, Frank Bille [EMAIL PROTECTED]: Sounds weird. Can you show me your apache conf for the proxy? Frank On Nov 9, 2007 12:44 PM, Murat Yücel [EMAIL PROTECTED] wrote: Hi Frank I have changed the /app/* to /* but it doesnt change the urls. They are still wrong. For example i enter the following url: www.wicket.com The url is transformed to www.wicket.com/wicket/?wicket:bookmarkablePage=%3Acom.wicket.LoginPage If i remove the the wicket part from the url then i can see the login page. But if i click on a link then the wicket part is appended again. /Murat 2007/11/9, Frank Bille [EMAIL PROTECTED]: First of all, you don't need /app/* anylonger. just /*. I'm running behind proxy as well and it works well. Are you sure you haven't run into this problem: http://cwiki.apache.org/WICKET/wicket-behind-a-front-end-proxy.html#Wicketbehindafront-endproxy-Whythisdoesn%2527talwayswork Frank On Nov 9, 2007 11:56 AM, Murat Yücel [EMAIL PROTECTED] wrote: Hi All I have looked at this article: http://cwiki.apache.org/WICKET/wicket-behind-a-front-end-proxy.html and it seems like the problem should be gone in wicket 1.3 but it isnt. I still get 404 errors. There is a warning on the wiki page: Don't use setContextPath with Wicket 1.3. I am not setting the context path. Instead i am using filter-mapping. Is this the same thing? filter-mapping filter-namewicket/filter-name !-- The app is needed for ajax (this is a known limitation/bug in wicket) -- url-pattern/app/*/url-pattern /filter-mapping Do you have a workaround for this issue or am i doing something wrong? I am currently running 1.3-beta4. Kind regards /Murat Yücel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Wicket behind a front-end proxy
It seems like wicket doesnt support it, because there is no workaround on the link that Frank Bille send. There is only information about that this is a problem. /Murat 2007/11/9, Johan Compagner [EMAIL PROTECTED]: so we dont support this currently? myserver1.xxx.com:80 - localhost:8080/myapp1 myserver2.xxx.com:80 - localhost:8080/myapp2 johan On Nov 9, 2007 1:35 PM, Frank Bille [EMAIL PROTECTED] wrote: Read this again: http://cwiki.apache.org/WICKET/wicket-behind-a-front-end-proxy.html#Wicketbehindafront-endproxy-Whythisdoesn%2527talwayswork Frank On Nov 9, 2007 1:26 PM, Murat Yücel [EMAIL PROTECTED] wrote: Hi Frank I have substituted my projectname with wicket. Below is the conf for the proxy part. VirtualHost * ServerAdmin [EMAIL PROTECTED] ServerName www.wicket.com ServerAlias wicket.com ProxyRequests off ProxyPreserveHost On RewriteEngine On # Indexes + Directory Root. DirectoryIndex index.html DocumentRoot /var/wicket.com # Logfiles ErrorLog /var/log/apache2/wicket-error.log CustomLog /var/log/apache2/wicket-access.log combined ProxyPass / http://127.0.0.1:8080/wicket/ ProxyPassReverse / http://127.0.0.1:8080/wicket/ ProxyPreserveHost On /VirtualHost 2007/11/9, Frank Bille [EMAIL PROTECTED]: Sounds weird. Can you show me your apache conf for the proxy? Frank On Nov 9, 2007 12:44 PM, Murat Yücel [EMAIL PROTECTED] wrote: Hi Frank I have changed the /app/* to /* but it doesnt change the urls. They are still wrong. For example i enter the following url: www.wicket.com The url is transformed to www.wicket.com/wicket/?wicket:bookmarkablePage=%3Acom.wicket.LoginPage If i remove the the wicket part from the url then i can see the login page. But if i click on a link then the wicket part is appended again. /Murat 2007/11/9, Frank Bille [EMAIL PROTECTED]: First of all, you don't need /app/* anylonger. just /*. I'm running behind proxy as well and it works well. Are you sure you haven't run into this problem: http://cwiki.apache.org/WICKET/wicket-behind-a-front-end-proxy.html#Wicketbehindafront-endproxy-Whythisdoesn%2527talwayswork Frank On Nov 9, 2007 11:56 AM, Murat Yücel [EMAIL PROTECTED] wrote: Hi All I have looked at this article: http://cwiki.apache.org/WICKET/wicket-behind-a-front-end-proxy.html and it seems like the problem should be gone in wicket 1.3 but it isnt. I still get 404 errors. There is a warning on the wiki page: Don't use setContextPath with Wicket 1.3. I am not setting the context path. Instead i am using filter-mapping. Is this the same thing? filter-mapping filter-namewicket/filter-name !-- The app is needed for ajax (this is a known limitation/bug in wicket) -- url-pattern/app/*/url-pattern /filter-mapping Do you have a workaround for this issue or am i doing something wrong? I am currently running 1.3-beta4. Kind regards /Murat Yücel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Wicket behind a front-end proxy
so we dont support this currently? myserver1.xxx.com:80 - localhost:8080/myapp1 myserver2.xxx.com:80 - localhost:8080/myapp2 johan On Nov 9, 2007 1:35 PM, Frank Bille [EMAIL PROTECTED] wrote: Read this again: http://cwiki.apache.org/WICKET/wicket-behind-a-front-end-proxy.html#Wicketbehindafront-endproxy-Whythisdoesn%2527talwayswork Frank On Nov 9, 2007 1:26 PM, Murat Yücel [EMAIL PROTECTED] wrote: Hi Frank I have substituted my projectname with wicket. Below is the conf for the proxy part. VirtualHost * ServerAdmin [EMAIL PROTECTED] ServerName www.wicket.com ServerAlias wicket.com ProxyRequests off ProxyPreserveHost On RewriteEngine On # Indexes + Directory Root. DirectoryIndex index.html DocumentRoot /var/wicket.com # Logfiles ErrorLog /var/log/apache2/wicket-error.log CustomLog /var/log/apache2/wicket-access.log combined ProxyPass / http://127.0.0.1:8080/wicket/ ProxyPassReverse / http://127.0.0.1:8080/wicket/ ProxyPreserveHost On /VirtualHost 2007/11/9, Frank Bille [EMAIL PROTECTED]: Sounds weird. Can you show me your apache conf for the proxy? Frank On Nov 9, 2007 12:44 PM, Murat Yücel [EMAIL PROTECTED] wrote: Hi Frank I have changed the /app/* to /* but it doesnt change the urls. They are still wrong. For example i enter the following url: www.wicket.com The url is transformed to www.wicket.com/wicket/?wicket:bookmarkablePage=%3Acom.wicket.LoginPage If i remove the the wicket part from the url then i can see the login page. But if i click on a link then the wicket part is appended again. /Murat 2007/11/9, Frank Bille [EMAIL PROTECTED]: First of all, you don't need /app/* anylonger. just /*. I'm running behind proxy as well and it works well. Are you sure you haven't run into this problem: http://cwiki.apache.org/WICKET/wicket-behind-a-front-end-proxy.html#Wicketbehindafront-endproxy-Whythisdoesn%2527talwayswork Frank On Nov 9, 2007 11:56 AM, Murat Yücel [EMAIL PROTECTED] wrote: Hi All I have looked at this article: http://cwiki.apache.org/WICKET/wicket-behind-a-front-end-proxy.html and it seems like the problem should be gone in wicket 1.3 but it isnt. I still get 404 errors. There is a warning on the wiki page: Don't use setContextPath with Wicket 1.3. I am not setting the context path. Instead i am using filter-mapping. Is this the same thing? filter-mapping filter-namewicket/filter-name !-- The app is needed for ajax (this is a known limitation/bug in wicket) -- url-pattern/app/*/url-pattern /filter-mapping Do you have a workaround for this issue or am i doing something wrong? I am currently running 1.3-beta4. Kind regards /Murat Yücel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Wicket behind a front-end proxy
Johan Compagner wrote: so we dont support this currently? myserver1.xxx.com:80 - localhost:8080/myapp1 myserver2.xxx.com:80 - localhost:8080/myapp2 We support that just fine. That, in fact, is most of the reason why we're using relative URLs in 1.3. Murat: I have this working perfectly fine on lots of hosts. What version of Apache do you have? Don't forget to add the ProxyPassReverseCookiePath directive in, or you may have issues with sessions. It sounds to me like your Apache isn't honouring the ProxyPassReverse directive. Explanation === When a request comes in to your Apache, it forwards it on using the ProxyPass configuration to your tomcat/jetty/whatever. If you're using a context path other than the root one, then that request looks like this: http://appserver:8080/contextPath/filterMapping/pageName or http://appserver:8080/contextPath/filterMapping/?wicket:interface=[...] etc. The appserver doesn't know anything about your proxy, so when it does a 302 redirect, it will do it to somewhere like this: /contextPath/filterMapping/?wicket:interface=[...] Apache is then responsible for converting the URL in the 302 redirect into the proxied-version. It does this using the ProxyPassReverse config. In the above example, it'll need to rewrite /contextPath/ to / ProxyPassReverseCookiePath is used to do the same thing with any cookies in the response. Cookies have a URL/domain, and your Tomcat will set them at /contextPath/, so that also needs rewriting to / otherwise the browser won't send them on the next request, which means your session won't work. Murat: My suggestion to you is to strip out all the other config from your VirtualHost (all the RewriteEngine stuff, etc.) and first get it working using the basic set-up on the wiki-page. This does work. Regards, Al - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
