The server name is required because if you don't supply it, it would have to come to the Host header which is set by the user's agent. And we don't trust users :-)
On Thu, Feb 3, 2011 at 4:06 AM, Kristian Rink <[email protected]> wrote: > Folks; > > first off, thanks a bunch for your support on that. Much appreciated. :) > > Am Thu, 03 Feb 2011 16:22:24 +1100 > schrieb Steve Swinsburg <[email protected]>: > > > On 03/02/2011, at 3:04 PM, Scott Battaglia wrote: > > > > 1. Hardcoded values in web.xml > > > 2. JNDI lookup > > > 3. Spring Dependency Injection > > > > > > One of those should be able to support your needs. The last two > > > separate the configuration from the generated WAR. > > Well yes, I am aware of that. :) And, as a matter of fact, "hard-coded > values in web.xml" are perfectly fine with me. > > My question was more, like, whether or not these hard-coded values in > web.xml have to be absolute values (including http://<server-name>/...) > or might as well be relative values, assuming the CAS stuff is running > on / reachable via HTTP on the same (logical/physical) server and via > the same protocol scheme (HTTP, HTTPS). The idea to use maven2 > filtering in order to set the "appropriate absolute values" in web.xml > at packaging time is good workaround to me, at the moment. > > > > In both cases, Maven can be used to provide build time filtering and > > enable reuse of code on different servers. So I suggested that this > > be added to the CAS server by default, since it is useful > > functionality. > > Yes, it definitely is. > > Cheers & thanks again, > Kristian > > -- > You are currently subscribed to [email protected] as: > [email protected] > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-user > -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
