tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christopher Schultz <ch...@christopherschultz.net>
Subject Re: tomcat on windows 2012 weirdness
Date Thu, 18 Dec 2014 17:42:59 GMT
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Cris,

On 12/18/14 12:22 PM, Cris Berneburg - US wrote:
> Chris
> 
> cb> I interpret this to mean that my local IE browser thinks the 
> cb> intranet web site that I access either by name or by IP is 
> actually cb> 2 different sites in 2 different security zones.  I 
> will try to cb> adjust my browser security settings and see if
> that makes any differences.
> 
> cs> That sounds plausible. If IE changes its cookie policy based 
> upon those zones, then you may have found the issue. I wonder if 
> your local policy whitelists a certain IP range but doesn't use 
> hostnames, which may account for the difference.
> 
> Turning off IE Compatibility Mode for intranet sites did boost the 
> request header User-Agent from "Mozilla/4.0" to "Mozilla/5.0", but 
> the browser still would not accept cookies.  I have since found
> the source of the problem and the solution, which I will send in a 
> follow-up message.

Looking forward to it.

> cs> Time to ask your webapp software vendor to fix their web 
> application cs> so it can be used without cookies ;)
> 
> Ouch!  I *am* the software developer for this web application. :-)

Well, the good news is that there's a chance it'll get done. Sometimes
3rd-party vendors will just say "sorry, we simply don't support that
configuration; use a supported configuration" which is a lousy answer IMO.

You can also fix the application as you go; you don't have to do 100%
of it all at once... nobody has noticed before, so nobody will notice
if you do 10% of it and then sit on it for a while.

There's no better time to start fixing your URLs than now, so every
time you have to edit a HTML template, just fix the URLs in that file.
Here's the recipe you want:

Change

   <a href="/foo/bar">...</a>

to

  <a href="<%= request.getContextPath() +
response.encodeURL("/foo/bar") %>">...</a>

Better yet, use JSTL:

  <a href="<c:url value="/foo/bar"/>">...</a>

Then you don't need to see all that nasty Java stuff.

Remember you also want to fix <img>, <script>, <link>, <base>...
everything that can have a URL.

- -chris

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: GPGTools - http://gpgtools.org

iQIcBAEBCAAGBQJUkxIjAAoJEBzwKT+lPKRYfngP/2nZtpB8UdyGL2FkzzzKqG+c
SRo8+Mx2KAYbGXudGhijbZojvfNqv8R1/qfUPzDDZEXmPnKKp9lEZEKY3ppwBFA6
VoBXkFXiLlppIRT9S0LHEWPeinT8wRNH9recSvSAmfFE8PaTDE8vuZ/jeohI4kFs
YXu8IhTfPsc9Yuxgrx5UxPRvjWFZuvySotxvsHj65TSh28TRebk4xWlBsUDxkRM1
INLpjh7IqgudFXa4oikxBxnNXArtRwrq3KnsDwqCHTA3xKle8q2Ye6wFMf4y3TMc
i1uqjHjIHpg01n7TKOvzwUTGL9YpQHNgGl1jYZYrfiB21/QNFpKyPD6y3RiLOjLT
p532xmV9zo+tYpTl8wvv9v7Bo3lo3DxDRweJSyVf7BUtxdNpNMlIqMiR8NLG4V0n
YDDN2IxD+3X9vETcj+LyeLNMcJy5vA7m2tyeErymB8SZ7d8unw0K/mhILuGGjpIF
EQ0Yw/2NtPXOZR4bxB3yyV4gMgAe+7D3xLynwal+RVqwWk6Bui/eo68fQnlgwwa2
BD9gYoA7mketZ7p/JhM2wyxWOZVXnD0nf/vayj8i2+w6WvSaTxzDbDJ0+QOw3PvE
9ryk16P04XotlaBewGrDoZDsbsrlIlTLaR0UtaTfLX4EWZRWXARRYQZVKvj/lm4F
z/KPPejPgYTk6XgrBJxA
=Y7yF
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


Mime
View raw message