DO NOT REPLY [Bug 36895] New: - get_most_suitable_worker is called twice for a single request

gzilla/show_bug.cgi?id=36895 Summary: get_most_suitable_worker is called twice for a single request Product: Tomcat 5 Version: 5.0.28 Platform: PC OS/Version: Linux Status: NEW Severity: normal Priori

DO NOT REPLY [Bug 36837] New: - Looking for ProxyHandler implementation of Http request

gzilla/show_bug.cgi?id=36837 Summary: Looking for ProxyHandler implementation of Http request Product: Tomcat 5 Version: Unknown Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P2 Com

Re: Need an option to severe socket connections between mod_jk and ajp connector after request/response cycle.

they will close the connection after each request-response cycle) or set cachesize to 0 which will use ajp13 protocol, but I think it will close connections after each request too. I hope you don't use HTTP keep alive? Also: I vaguely remember there was an experimental connector/thread

Re: Problems Parsing Request Paramers

Yoav Shapira wrote: Hi, Could it be the referer URL is too long, causing the query string to be ignored or dropped? There's a limit (2048 characters, I think?) on GET requests in some browsers. But actually, you're seeing this on the server, so I'm not sure. Can you try testing with less para

RE: Problems Parsing Request Paramers

2005 2:06 PM To: Tomcat Developers List Subject: Re: Problems Parsing Request Paramers Hi, Could it be the referer URL is too long, causing the query string to be ignored or dropped? There's a limit (2048 characters, I think?) on GET requests in some browsers. But actually, you're see

Re: Problems Parsing Request Paramers

against submitted data. In the > event of a failure on the sanity checks, page is redirected back to > previous page. > > Simple enough. Well, users are filling out the form and clicking submit > with valid infromation, yet when I parse the parameters out of the > request, I

Problems Parsing Request Paramers

form and clicking submit with valid infromation, yet when I parse the parameters out of the request, I'm finding none of the form values from the previous page. I then decided to investigate further and log out all request information in the event that these sanity checks fail.

Need an option to severe socket connections between mod_jk and ajp connector after request/response cycle.

an provide hard facts, you are more than welcome. 1. The 1.3 generation of Apache web servers will spawn a child process to handle an HTTP request. Only one HTTP request at a time can be processed by that child. 2. As the load increases on the web server, additional child processes will

DO NOT REPLY [Bug 36827] - Need an option to severe socket connections between mod_jk and ajp connector after request/response cycle.

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 36827] New: - Need an option to severe socket connections between mod_jk and ajp connector after request/response cycle.

gzilla/show_bug.cgi?id=36827 Summary: Need an option to severe socket connections between mod_jk and ajp connector after request/response cycle. Product: Tomcat 5 Version: 5.0.28 Platform: All OS/Version: Linux Statu

DO NOT REPLY [Bug 35461] - bad request http 400 using mod_jk 1.2.13. After downgrading to 1.3.33 and mod_jk 1.2.5 the problems have gone. Problems occur again after using the combination Apache Webserver 1.3.33 and mod_jk 1.2.10

dump example, mod_jk has decided to send the request to a different worker than the one in the cookie for some reason. Otherwise, they are perfectly normal POST request records. Probably, somebody is going to have to be able to reproduce this with 'JkLogLevel debug' (or even 'J

DO NOT REPLY [Bug 35461] - bad request http 400 using mod_jk 1.2.13. After downgrading to 1.3.33 and mod_jk 1.2.5 the problems have gone. Problems occur again after using the combination Apache Webserver 1.3.33 and mod_jk 1.2.10

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 35461] - bad request http 400 using mod_jk 1.2.13. After downgrading to 1.3.33 and mod_jk 1.2.5 the problems have gone. Problems occur again after using the combination Apache Webserver 1.3.33 and mod_jk 1.2.10

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 36655] - mod_jk 1.2.12+ does not submit correct request port number to tomcat

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 36655] New: - mod_jk 1.2.12+ does not submit correct request port number to tomcat

gzilla/show_bug.cgi?id=36655 Summary: mod_jk 1.2.12+ does not submit correct request port number to tomcat Product: Tomcat 4 Version: 4.1.31 Platform: Other OS/Version: Solaris Status: NEW Severity:

DO NOT REPLY [Bug 35641] - Error decoding request in Tomcat server on submit of a jsp page

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 35641] - Error decoding request in Tomcat server on submit of a jsp page

NVALID | --- Additional Comments From [EMAIL PROTECTED] 2005-09-08 23:39 --- I am getting the exact same problem. When will this be fixed? Is there a new release slated soon? Sep 8, 2005 2:55:53 PM org.apache.jk.common.HandlerRequest invoke SEVERE: Error decoding request java.io.IOException

DO NOT REPLY [Bug 35461] - bad request http 400 using mod_jk 1.2.13. After downgrading to 1.3.33 and mod_jk 1.2.5 the problems have gone. Problems occur again after using the combination Apache Webserver 1.3.33 and mod_jk 1.2.10

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 36385] - [mod_jk1.2.14] Prepost pings are not sent before the first request

gzilla/show_bug.cgi?id=36385 --- Additional Comments From [EMAIL PROTECTED] 2005-09-02 16:53 --- (In reply to comment #9) > at least you could be sure some sort of code in the request handler is still > alive and running. Yes, it means the acceptor thread has managed to allocate a proc

DO NOT REPLY [Bug 36385] - [mod_jk1.2.14] Prepost pings are not sent before the first request

gzilla/show_bug.cgi?id=36385 --- Additional Comments From [EMAIL PROTECTED] 2005-09-02 14:43 --- at least you could be sure some sort of code in the request handler is still alive and running. Not a 100% guarantee of course :( -- Configure bugmail: http://issues.apache.org/bugzilla/userpre

DO NOT REPLY [Bug 36385] - [mod_jk1.2.14] Prepost pings are not sent before the first request

t; I got case where the tomcat was able to do the accept but was in serious > trouble > at a later time, and didn't process the request. Ok, but I don't see a way to guarantee that a Tomcat will process a request. Answering a pong right after an accept does not add much. -- Conf

DO NOT REPLY [Bug 36385] - [mod_jk1.2.14] Prepost pings are not sent before the first request

this one could be hang and that was the ping/pong goal, detect a zombie or hanged tomcat. I got case where the tomcat was able to do the accept but was in serious trouble at a later time, and didn't process the request. > IMO there is no point of sending cping/cpong if new connection &g

DO NOT REPLY [Bug 36385] - [mod_jk1.2.14] Prepost pings are not sent before the first request

repost_timeout and not connect_timeout, there is no cping/cpong before the first request (at least, if this is the intended behavior, a remark should be make in the documentation). -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail be

DO NOT REPLY [Bug 36385] - [mod_jk1.2.14] Prepost pings are not sent before the first request

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 36385] - [mod_jk1.2.14] Prepost pings are not sent before the first request

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 36385] - [mod_jk1.2.14] Prepost pings are not sent before the first request

{ /* * After we are connected, each error that we are going to * have is probably unrecoverable Don't send a ping before request if a ping as been send during connect ! -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- Y

DO NOT REPLY [Bug 36385] - [mod_jk1.2.14] Prepost pings are not sent before the first request

ct_timeout and you've set prepost_timeout (asking for a ping to be sent before every request), no ping will be sent before the first request. Here's an alternative patch (against mod_jk 1.2.14) that I hope better illustrates what I'm trying to say: < START OF PATCH > --- j

DO NOT REPLY [Bug 36385] - [mod_jk1.2.14] Prepost pings are not sent before the first request

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

[mod_jk1.2.14] Prepost pings are not sent before the first request (bug 36385)

Hi all, I've submitted a bug report to the ASF bugzilla but since the status of the bug hasn't changed since then (and since it is so trivial to fix) I've decided to ask you guys if I didn't follow the submitting protocol correctly or something. I've submitted a patch inline with the bug report

DO NOT REPLY [Bug 36385] New: - [mod_jk1.2.14] Prepost pings are not sent before the first request

gzilla/show_bug.cgi?id=36385 Summary: [mod_jk1.2.14] Prepost pings are not sent before the first request Product: Tomcat 5 Version: Unknown Platform: All OS/Version: All Status: NEW Severity: normal Pr

DO NOT REPLY [Bug 35461] - bad request http 400 using mod_jk 1.2.13. After downgrading to 1.3.33 and mod_jk 1.2.5 the problems have gone. Problems occur again after using the combination Apache Webserver 1.3.33 and mod_jk 1.2.10

gzilla/show_bug.cgi?id=35461 --- Additional Comments From [EMAIL PROTECTED] 2005-08-02 14:29 --- (In reply to comment #3) > Hmm, > This seems like you are using 'application/x-www-form-urlencoded' > with GET request. > Can you post the full mod_jk log from the beggining

DO NOT REPLY [Bug 35461] - bad request http 400 using mod_jk 1.2.13. After downgrading to 1.3.33 and mod_jk 1.2.5 the problems have gone. Problems occur again after using the combination Apache Webserver 1.3.33 and mod_jk 1.2.10

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 35461] - bad request http 400 using mod_jk 1.2.13. After downgrading to 1.3.33 and mod_jk 1.2.5 the problems have gone. Problems occur again after using the combination Apache Webserver 1.3.33 and mod_jk 1.2.10

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 35461] - bad request http 400 using mod_jk 1.2.13. After downgrading to 1.3.33 and mod_jk 1.2.5 the problems have gone. Problems occur again after using the combination Apache Webserver 1.3.33 and mod_jk 1.2.10

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 35461] - bad request http 400 using mod_jk 1.2.13. After downgrading to 1.3.33 and mod_jk 1.2.5 the problems have gone. Problems occur again after using the combination Apache Webserver 1.3.33 and mod_jk 1.2.10

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 35461] - bad request http 400 using mod_jk 1.2.13. After downgrading to 1.3.33 and mod_jk 1.2.5 the problems have gone. Problems occur again after using the combination Apache Webserver 1.3.33 and mod_jk 1.2.10

gzilla/show_bug.cgi?id=35461 --- Additional Comments From [EMAIL PROTECTED] 2005-08-01 11:08 --- Hmm, This seems like you are using 'application/x-www-form-urlencoded' with GET request. Can you post the full mod_jk log from the beggining of the transaction to the end for that req

DO NOT REPLY [Bug 35461] - bad request http 400 using mod_jk 1.2.13. After downgrading to 1.3.33 and mod_jk 1.2.5 the problems have gone. Problems occur again after using the combination Apache Webserver 1.3.33 and mod_jk 1.2.10

would be very kind if you would reinvestigate: 29.07.2005 15:55:00 org.apache.jk.common.HandlerRequest invoke SCHWERWIEGEND: Error decoding request java.net.SocketTimeoutException: Read timed out at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStrea

DO NOT REPLY [Bug 35461] - bad request http 400 using mod_jk 1.2.13. After downgrading to 1.3.33 and mod_jk 1.2.5 the problems have gone. Problems occur again after using the combination Apache Webserver 1.3.33 and mod_jk 1.2.10

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 35270] - RequestDispatcher forward not handling a ServletRequestWrapper correctly when updating forward request params

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 35270] - RequestDispatcher forward not handling a ServletRequestWrapper correctly when updating forward request params

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 35896] - Tomcat stoped service apache request

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 35896] - Tomcat stoped service apache request

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 35896] - Tomcat stoped service apache request

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 35896] - Tomcat stoped service apache request

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 35896] - Tomcat stoped service apache request

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 35896] New: - Tomcat stoped service apache request

gzilla/show_bug.cgi?id=35896 Summary: Tomcat stoped service apache request Product: Tomcat 3 Version: 3.3.2 Final Platform: Other OS/Version: other Status: NEW Severity: normal Priority: P2 Component: Conn

DO NOT REPLY [Bug 34818] - Request alternating color scheme for html manager

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 34818] - Request alternating color scheme for html manager

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 34818] - Request alternating color scheme for html manager

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 34818] - Request alternating color scheme for html manager

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 34818] - Request alternating color scheme for html manager

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 34818] - Request alternating color scheme for html manager

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 35709] - allow to create a short-lived secondary session from a request to prevent cross-site scripting-like attacks

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 35641] - Error decoding request in Tomcat server on submit of a jsp page

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 35641] - Error decoding request in Tomcat server on submit of a jsp page

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 34818] - Request alternating color scheme for html manager

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 35775] - GET - request parameter parsing fails with german umlaute.

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 35775] - GET - request parameter parsing fails with german umlaute.

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 35709] - allow to create a short-lived secondary session from a request to prevent cross-site scripting-like attacks

omment suggests that resources play an important role in judging the > validity of the request. I would suggest that the resource question is > deferred > until later i.e. considered when this is due after evaluation, i.e. in a > cooperative fashion compatible with the structure of

DO NOT REPLY [Bug 35709] - allow to create a short-lived secondary session from a request to prevent cross-site scripting-like attacks

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 35709] - allow to create a short-lived secondary session from a request to prevent cross-site scripting-like attacks

udging the validity of the request. I would suggest that the resource question is deferred until later i.e. considered when this is due after evaluation, i.e. in a cooperative fashion compatible with the structure of this project. Voting after evaluation comes to mind. 3) "There are gaping hol

DO NOT REPLY [Bug 35709] - allow to create a short-lived secondary session from a request to prevent cross-site scripting-like attacks

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 35709] - allow to create a short-lived secondary session from a request to prevent cross-site scripting-like attacks

from a|lived secondary session from |request to prevent cross- |a request to prevent cross- |site scripting |site scripting-like attacks --- Additional Comments From [EMAIL PROTECTED] 2005-07-18 14:21 --- cookies might not be a good

DO NOT REPLY [Bug 35775] - GET - request parameter parsing fails with german umlaute.

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 35775] - GET - request parameter parsing fails with german umlaute.

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 35775] New: - GET - request parameter parsing fails with german umlaute.

gzilla/show_bug.cgi?id=35775 Summary: GET - request parameter parsing fails with german umlaute. Product: Tomcat 5 Version: 5.0.28 Platform: PC OS/Version: Windows XP Status: NEW Severity: major Priori

Problem with request dispatcher

Hello, i'm having a problem with calling a servlet and dispatching to a jsp. my example: here is my simple html form: Login Password Here's my processing servlet: public class Test2 extends HttpServlet { public void doGet(HttpServletRequest request, HttpServl

DO NOT REPLY [Bug 35709] - allow to crate a short-lived secondary session from a request to prevent cross-site scripting

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 35709] - allow to crate a short-lived secondary session from a request to prevent cross-site scripting

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 35709] - allow to crate a short-lived secondary session from a request to prevent cross-site scripting

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 35709] New: - allow to crate a short-lived secondary session from a request to prevent cross-site scripting

gzilla/show_bug.cgi?id=35709 Summary: allow to crate a short-lived secondary session from a request to prevent cross-site scripting Product: Tomcat 5 Version: Nightly Build Platform: Other OS/Version: other Statu

DO NOT REPLY [Bug 35641] New: - Error decoding request in Tomcat server on submit of a jsp page

gzilla/show_bug.cgi?id=35641 Summary: Error decoding request in Tomcat server on submit of a jsp page Product: Tomcat 5 Version: 5.5.4 Platform: Other OS/Version: Windows XP Status: NEW Severity: b

DO NOT REPLY [Bug 35270] - RequestDispatcher forward not handling a ServletRequestWrapper correctly when updating forward request params

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 35461] - bad request http 400 using mod_jk 1.2.13. After downgrading to 1.3.33 and mod_jk 1.2.5 the problems have gone. Problems occur again after using the combination Apache Webserver 1.3.33 and mod_jk 1.2.10

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

Re: Feature Request: Optional No Cert validation on SSL connector

Yep, this is a problem. And, as I said, we don't have keystores, so even if it did pick up the new cert it still wouldn't work for us. jean-frederic clere wrote: OK I have added a new CA using: +++ [EMAIL PROTECTED]:~> $JAVA_HOME/bin/keytool -import -trustcacerts -file ~/CERTS/demoCA/cacert.

Re: Feature Request: Optional No Cert validation on SSL connector

Chad La Joie wrote: jean-frederic clere wrote: Chad La Joie wrote: Yeah, I know what mod-ssl says, and for most cases it's probably right, however the optional_no_ca option is interesting to us because it provides exactly the functionality that we need; accepting the client cert, putting it

Re: Feature Request: Optional No Cert validation on SSL connector

jean-frederic clere wrote: > Chad La Joie wrote: > >> Yeah, I know what mod-ssl says, and for most cases it's probably right, >> however the optional_no_ca option is interesting to us because it >> provides exactly the functionality that we need; accepting the client >> cert, putting it in a sta

Re: Feature Request: Optional No Cert validation on SSL connector

certificate, but instead of HTTPD trying to validate the cert, it just passes the cert on to the Shibboleth server. This allows us to validate the certificate against the cert chains in the metadata files within the server code (a huge support boon for us). What we'd like to request is a simila

Re: Feature Request: Optional No Cert validation on SSL connector

client to send its certificate, but >>> instead of HTTPD trying to validate the cert, it just passes the cert on >>> to the Shibboleth server. This allows us to validate the certificate >>> against the cert ch

Re: Feature Request: Optional No Cert validation on SSL connector

tificate, but instead of HTTPD trying to validate the cert, it just passes the cert on to the Shibboleth server. This allows us to validate the certificate against the cert chains in the metadata files within the server code (a huge support boon for us). What we'd like to request is a similar optio

Re: Feature Request: Optional No Cert validation on SSL connector

allows the client to send its certificate, but instead of HTTPD trying to validate the cert, it just passes the cert on to the Shibboleth server. This allows us to validate the certificate against the cert chains in the metadata files within the server code (a huge support boon for us). What we&

{TOML#001-926-078}Feature Request: Optional No Cert validation on SSL connector

Dear Customer, Thank you for your interest in the services offered by TimesofMoney.com.We have received your email. Our Customer Relations Officer will get in touch with you shortly. Assuring you of our best services always. Warm Regards, Customer Relations TimesofMoney.com A Times Group Com

{TOML#001-926-076}Feature Request: Optional No Cert validation on SSL connector

Dear Customer, Thank you for your interest in the services offered by TimesofMoney.com.We have received your email. Our Customer Relations Officer will get in touch with you shortly. Assuring you of our best services always. Warm Regards, Customer Relations TimesofMoney.com A Times Group Com

Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Feature Request: Optional No Cert validation on SSL connector

su correo ha sido recepcionado. gracias - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Feature Request: Optional No Cert validation on SSL connector

su correo ha sido recepcionado. gracias - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: Re: Re: Re: Re: Re: Re: Re: Re: Feature Request: Optional No Cert validation on SSL connector

su correo ha sido recepcionado. gracias - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: Re: Re: Re: Re: Re: Re: Re: Feature Request: Optional No Cert validation on SSL connector

su correo ha sido recepcionado. gracias - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: Re: Re: Re: Re: Re: Re: Feature Request: Optional No Cert validation on SSL connector

su correo ha sido recepcionado. gracias - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: Re: Re: Re: Re: Re: Feature Request: Optional No Cert validation on SSL connector

su correo ha sido recepcionado. gracias - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: Re: Re: Re: Re: Feature Request: Optional No Cert validation on SSL connector

su correo ha sido recepcionado. gracias - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: Re: Re: Re: Feature Request: Optional No Cert validation on SSL connector

su correo ha sido recepcionado. gracias - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: Re: Re: Feature Request: Optional No Cert validation on SSL connector

su correo ha sido recepcionado. gracias - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: Re: Feature Request: Optional No Cert validation on SSL connector

su correo ha sido recepcionado. gracias - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: Feature Request: Optional No Cert validation on SSL connector

ut > instead of HTTPD trying to validate the cert, it just passes the cert on > to the Shibboleth server. This allows us to validate the certificate > against the cert chains in the metadata files within the server code (a > huge support boon for us). What we'd like to request is a s

DO NOT REPLY [Bug 35461] - bad request http 400 using mod_jk 1.2.13. After downgrading to 1.3.33 and mod_jk 1.2.5 the problems have gone. Problems occur again after using the combination Apache Webserver 1.3.33 and mod_jk 1.2.10

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 35461] - bad request http 400 using mod_jk 1.2.13. After downgrading to 1.3.33 and mod_jk 1.2.5 the problems have gone. Problems occur again after using the combination Apache Webserver 1.3.33 and mod_jk 1.2.10

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

Feature Request: Optional No Cert validation on SSL connector

er code (a huge support boon for us). What we'd like to request is a similar option for the SSL connector when client cert auth is used so that we can support a stand alone Tomcat set up too. Would this be possible? -- Chad La Joie 315Q St. Mary's Hall Project Sent

DO NOT REPLY [Bug 35270] - RequestDispatcher forward not handling a ServletRequestWrapper correctly when updating forward request params

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 35270] - RequestDispatcher forward not handling a ServletRequestWrapper correctly when updating forward request params

gzilla/show_bug.cgi?id=35270 --- Additional Comments From [EMAIL PROTECTED] 2005-06-08 17:44 --- I was able to reproduce this same bug on Tomcat 5.5.9 as well. The javax.servlet.forward.request_uri attribute is definitely NOT being set correctly when forwarding with a wrapped r

DO NOT REPLY [Bug 35270] - RequestDispatcher forward not handling a ServletRequestWrapper correctly when updating forward request params

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

  1   2   3   4   5   6   7   8   9   10   >