On Feb 14, 2006, at 9:38 PM, Eelco Hillenius wrote:
It seems that it is a bit tricky to buid Wicket apps that both have ssl and normal content mixed. We could ease the pain a bit by using absolute instead of relative urls everywhere, and having a call back method (e.g. in RequestCycle) that returns the schema and port. Can you think of potential problems with this? Eelco
I've been using a framework defaulting to absolute urls, and that was always a pain when application had to be load balanced behind a proxy or server had to be accessed with different addresses from different networks (because of exotic network configurations found on many big companies.)
Server name and port cannot really be automatically detected, so they have to be configured somewhere, and when host name is configured somewhere it gets trickier to deploy same package to test and production environments.
In most use cases it's really simpler to use https all the time and not bounce between http and https.
It's ok to have these things configured somewhere, but I don't want wicket to use absolute urls by default, it really brings more pain in many cases.
-- Janne Hietamäki Cemron Ltd http://www.cemron.fi/ ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642 _______________________________________________ Wicket-develop mailing list Wicket-develop@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-develop
