-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Steffen,
On 3/2/13 1:53 PM, Steffen Heil (Mailinglisten) wrote:
> Is there any interest for that feature in the community and any
> chance to get such a patch accepted into the codebase?
There's always this:
https://issues.apache.org/bugzilla/show
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jose,
On 3/2/13 2:25 PM, Jose María Zaragoza wrote:
>> The moral of the story is that nested URL spaces is a bad idea
>> where sessions are concerned. We easily fixed that problem by
>> moving the /-mounted webapp to a unique URL prefix (which wasn'
On 02/03/2013 18:53, Steffen Heil (Mailinglisten) wrote:
> Hi
>
> I looked into the source of tomcat 7 (7.0.x trunk) to extend it to support
> wildcard aliases (such as *.example.com).
> I found the class org.apache.tomcat.util.http.mapper.Mapper.
> Looking at it, I found a small bug (lines 210-21
> The moral of the story is that nested URL spaces is a bad idea where
> sessions are concerned. We easily fixed that problem by moving the
> /-mounted webapp to a unique URL prefix (which wasn't trivial, since
> we had inter-webapp links, etc.) but it solved all of those weird
> problems.
Thanks.
Hi
I looked into the source of tomcat 7 (7.0.x trunk) to extend it to support
wildcard aliases (such as *.example.com).
I found the class org.apache.tomcat.util.http.mapper.Mapper.
Looking at it, I found a small bug (lines 210-213):
if (pos < 0) {
log.error("No host found: " +
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
All,
Motivated by seeing Rainer's presentation at ApacheCon 2013,
"Monitoring Apache Tomcat and the Apache Web" [1], I started looking
at mod_jk's status worker - particularly the XML output as I believe
it will be the easiest format to parse for mo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Vihari,
On 3/1/13 2:15 AM, Vihari Piratla wrote:
> I did perform any of the steps that I am supposed if I got to use
> log4j
Do you mean that you *did* configure Tomcat for log4j, or that you
didn't? If you did, what does the Tomcat (global) log4j.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Nick,
On 3/1/13 2:58 PM, Nick Williams wrote:
> Browsers send all of the cookies because that's the compliant thing
> to do. RFC-2109 [1] says:
>
>> If multiple cookies satisfy the criteria above, they are ordered
>> in the Cookie header such that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jose,
On 3/1/13 2:46 PM, Jose María Zaragoza wrote:
> I wonder why browsers don't send only one JSESSIONID If I request
> an URL as www.mydomain.com/app/myapplication/action.do and it has
> got 2 cookies with the same name, one for www.mydomain.com/
