/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
Priority: P2
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 pool
implementation
/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
Component
/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
Status: NEW
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 be spawned
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. The following is what I
logged out
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'm finding none of the form values from the previous page. I
then decided to investigate further and log out all request information
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 seeing this on the
server, so I'm not sure. Can
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
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=35461.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
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 'JkLogLevel trace' :) to get some idea why
the POST body wasn't
/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: major
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=36655.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
|
--- 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 TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=35641.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=35461.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=36385.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
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
--- jk_ajp_common.c 2005-09-02 10:22
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
--- You are receiving this mail because: ---
You are the assignee
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=36385.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=36385.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
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 because: ---
You are the assignee for the bug, or are watching
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
is established. It makes sense only with already
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.
--
Configure bugmail: http://issues.apache.org/bugzilla
/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/userprefs.cgi
/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 processor thread
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
/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
Priority: P3
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=35461.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=35461.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=35461.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
/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 of the transaction
to the end
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=35461.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
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.SocketInputStream.read
/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 request. There must
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=35461.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=35270.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=35270.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=35896.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=35896.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
/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: Connectors
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=35896.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=35896.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=35896.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=34818.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=34818.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=34818.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=34818.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=34818.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=34818.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=34818.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=35641.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=35641.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=35709.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
/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
Priority: P2
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=35775.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=35775.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
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 answer
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=35709.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
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 holes in session security (without SSL
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=35709.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
!= cross site scripting vulnerability.
I am talking about setting a session cookie for another domain, not reading
cookies.
2)
You seem to have a bit too much time on your hands.
This comment suggests that resources play an important role in judging the
validity of the request. I would suggest
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=35775.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=35775.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
my processing servlet:
public class Test2 extends HttpServlet
{
public void doGet(HttpServletRequest request, HttpServletResponse response)
throws IOException, ServletException
{
System.err.println(test: doGet());
getServletContext().getRequestDispatcher(/index2
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=35709.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
/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
Status: NEW
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=35709.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=35709.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
/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: blocker
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=35270.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=35461.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
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
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
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 similar
option
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
option for the SSL connector when client cert auth
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'd like to request
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
option for the SSL connector when client cert auth is used so that we
can
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 standard
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
option for the SSL connector when client cert auth is used so that we
can
su correo ha sido recepcionado. gracias
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
su correo ha sido recepcionado. gracias
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
su correo ha sido recepcionado. gracias
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
su correo ha sido recepcionado. gracias
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
su correo ha sido recepcionado. gracias
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
su correo ha sido recepcionado. gracias
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
su correo ha sido recepcionado. gracias
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
su correo ha sido recepcionado. gracias
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
su correo ha sido recepcionado. gracias
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
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
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
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=35461.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=35461.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
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 Sentinel 202.687.0124
/show_bug.cgi?id=35270
Summary: RequestDispatcher forward not handling a
ServletRequestWrapper correctly when updating forward
request params
Product: Tomcat 5
Version: 5.0.28
Platform: PC
OS/Version: Windows XP
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=35270.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
/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 request
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=35270.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=33911.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=33911.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
1 - 100 of 887 matches
Mail list logo