Christopher Schultz chris at christopherschultz.net writes:
[...]
| problem is, none of these approaches work in Tomcat 5.5. For 1), this
simply
| didn't have any effect for me. 2) neither, maybe Tomcat simply ignores
that
| property?
How did you set the property?
I am running my web
Christopher, thanks a lot for your replies.
Christopher Schultz chris at christopherschultz.net writes:
MK wrote:
| Actually I don't even call URL.openConnection, because I don't need it
at all.
| It's really just that the java.net.URL constructor requires that there
exists an
| object
MK kaeppler.matthias at nts.ricoh.co.jp writes:
[...]
I am using Tomcat 5.5 by the way.
I will try rolling a jar from my protocol handler and put it in the places you
suggested. Maybe that'll work, I'll report back.
actually I just realized that this is not gonna help if Tomcat does
Hi tomcat users,
I was wondering whether it's possible to advise Tomcat to dump any incoming HTTP
requests while preserving their original plain text nature? I tried hard to find
something like this, but I only stumbled upon the RequestDumperValve, which
unfortunately only has access to a request
Actually, I found a solution, but it is specific to WinHTTP:
http://msdn2.microsoft.com/en-us/library/aa384119(VS.85).aspx
It worked perfectly for me, and I found the error I was hunting down for 2
hours... So in this regard, I'm fine now.
But still, I am curious whether there is a server-side
Christopher Schultz chris at christopherschultz.net writes:
Praveen,
pmanvi wrote:
| I found that org.apache.catalina.loader.WebappLoader was setting the
| URL.setURLStreamHandlerFactory() with DirContextURLStreamHandlerFactory,
| basically jndi stream handler.
| I updated this file
