Okay, I will try that. I have the properties log level currently set to
"debug". I'll try trace and see if it can provide more information there
(I didn't realize trace had more information then debug).
Yeah, I don't understand it either. It's important to note that this
*only* happens when using the Default Document (no actual file name in
the URL). As long as a filename is present in the URL, cookie headers
are passed off perfectly. So... I'm just trying to see where the cookie
header actually gets lost.
I've tried both ways I know of for getting a tomcat-processed file set
as a default document in IIS7 - a script map and a custom module
mapping, and both methods have this problem.
Thank you for your help!
Warm regards,
Jordan Michaels
Vivio Technologies
http://www.viviotech.net/
Open BlueDragon Steering Committee
Railo Community Distributions
Rainer Jung wrote:
On 03.04.2010 01:03, Jordan Michaels wrote:
Hello!
I'm attempting to debug a cookie problem with the IIS7, using a default
document, and the Tomcat connector.
I can see where firefox is sending cookie information in the request
headers to IIS, and I can see where the isapi_connector is passing the
request off to Tomcat *without* cookie information, but is there any way
to see what IIS is passing to the isapi_redirect DLL?
Knowing what's being passed to the connector would tell me if it's an
IIS7 problem or a connector problem.
Thanks for any help you can offer!
Best you can do is setting the log_level to trace. That will produce a
lot of output. It won't show you what the plugin gets from IIS, but what
we send to Tomcat from the point of view of the plugin. I can't see how
we would change anything about cookies, because cookies for the plugin
are just HTTP headers and as such are logged when forwarded to Tomcat.
Except for the JSESSIONID cookie which in addition gets inspected for
load balancing stickyness decisions.
Regards,
Rainer
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
