DO NOT REPLY [Bug 29671] - Context don't start with multiple HTTP 1.1 connectors

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

[SECURITY ISSUE] Using allowLinking with deprecated HTTP 1.1 connector

All, A security issue has come to light where a mal-formed request may result in JSP source code disclosure. This issue only applies if all of the following are true: 1. You are using any Tomcat 4 version >= 4.1.15 2. You are using the deprecated HTTP 1.1 connec

DO NOT REPLY [Bug 32672] New: - IIS Stops after - GET /WEB-INF./web.xml http/1.1 -

gzilla/show_bug.cgi?id=32672 Summary: IIS Stops after - GET /WEB-INF./web.xml http/1.1 - Product: Tomcat 5 Version: Unknown Platform: PC OS/Version: Windows 2000 Status: NEW Severity: blocker Priority: P2 Com

DO NOT REPLY [Bug 32672] - IIS Stops after - GET /WEB-INF./web.xml http/1.1 -

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 29671] - Context don't start with multiple HTTP 1.1 connectors

gzilla/show_bug.cgi?id=29671 Context don't start with multiple HTTP 1.1 connectors --- Additional Comments From [EMAIL PROTECTED] 2004-08-21 19:25 --- You copy the jxmri.jar to $CATALINA_HOME/bin/jmx.jar (leaving the name as 'jmx.jar' to avoid havi

DO NOT REPLY [Bug 29671] - Context don't start with multiple HTTP 1.1 connectors

gzilla/show_bug.cgi?id=29671 Context don't start with multiple HTTP 1.1 connectors --- Additional Comments From [EMAIL PROTECTED] 2004-08-21 07:54 --- Could you please elaborate on: > Please try with the JMX RI 1.2. I got to here http://wwws.sun.com/software/communitysource/jmx

DO NOT REPLY [Bug 29671] - Context don't start with multiple HTTP 1.1 connectors

gzilla/show_bug.cgi?id=29671 Context don't start with multiple HTTP 1.1 connectors [EMAIL PROTECTED] changed: What|Removed |Added CC||[EMAI

DO NOT REPLY [Bug 29671] - Context don't start with multiple HTTP 1.1 connectors

gzilla/show_bug.cgi?id=29671 Context don't start with multiple HTTP 1.1 connectors [EMAIL PROTECTED] changed: What|Removed |Added Status|REOPENED

DO NOT REPLY [Bug 29671] - Context don't start with multiple HTTP 1.1 connectors

gzilla/show_bug.cgi?id=29671 Context don't start with multiple HTTP 1.1 connectors [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED

DO NOT REPLY [Bug 29671] - Context don't start with multiple HTTP 1.1 connectors

gzilla/show_bug.cgi?id=29671 Context don't start with multiple HTTP 1.1 connectors [EMAIL PROTECTED] changed: What|Removed |Added CC||[EMAI

DO NOT REPLY [Bug 30460] - org.apache.coyote.tomcat5.MapperListener init -> Error registering contexts -> HTTP 1.1 connectors pauses

gzilla/show_bug.cgi?id=30460 org.apache.coyote.tomcat5.MapperListener init -> Error registering contexts -> HTTP 1.1 connectors pauses [EMAIL PROTECTED] changed: What|Removed

DO NOT REPLY [Bug 30460] New: - org.apache.coyote.tomcat5.MapperListener init -> Error registering contexts -> HTTP 1.1 connectors pauses

gzilla/show_bug.cgi?id=30460 org.apache.coyote.tomcat5.MapperListener init -> Error registering contexts -> HTTP 1.1 connectors pauses Summary: org.apache.coyote.tomcat5.MapperListener init -> Error registering contexts -> HTTP 1.1 connectors pauses

DO NOT REPLY [Bug 30273] - The HTTP 1.1 processor ignores "Connection: close" on response

gzilla/show_bug.cgi?id=30273 The HTTP 1.1 processor ignores "Connection: close" on response --- Additional Comments From [EMAIL PROTECTED] 2004-07-28 10:12 --- If M$ no longer supports connection keep-alive properly (!!! can you actually give details on what's broken exactly

DO NOT REPLY [Bug 30273] - The HTTP 1.1 processor ignores "Connection: close" on response

gzilla/show_bug.cgi?id=30273 The HTTP 1.1 processor ignores "Connection: close" on response --- Additional Comments From [EMAIL PROTECTED] 2004-07-28 06:07 --- While I will not reopen this bug, I simply want to put my $0.10 cents in here (there's more than $0.02 cents of mater

DO NOT REPLY [Bug 30273] - The HTTP 1.1 processor ignores "Connection: close" on response

gzilla/show_bug.cgi?id=30273 The HTTP 1.1 processor ignores "Connection: close" on response --- Additional Comments From [EMAIL PROTECTED] 2004-07-22 22:33 --- There are a lot of other things: transfer encoding, content encoding, etc. I don't want to start touching these funct

DO NOT REPLY [Bug 30273] - The HTTP 1.1 processor ignores "Connection: close" on response

gzilla/show_bug.cgi?id=30273 The HTTP 1.1 processor ignores "Connection: close" on response --- Additional Comments From [EMAIL PROTECTED] 2004-07-22 22:24 --- In matters of how the an HTTP connector should work, I think RFC2616 should have the final say - but as I don't have

DO NOT REPLY [Bug 30273] - The HTTP 1.1 processor ignores "Connection: close" on response

gzilla/show_bug.cgi?id=30273 The HTTP 1.1 processor ignores "Connection: close" on response --- Additional Comments From [EMAIL PROTECTED] 2004-07-22 22:07 --- While I do respect your opinion, I disagree with that.

DO NOT REPLY [Bug 30273] - The HTTP 1.1 processor ignores "Connection: close" on response

gzilla/show_bug.cgi?id=30273 The HTTP 1.1 processor ignores "Connection: close" on response --- Additional Comments From [EMAIL PROTECTED] 2004-07-22 22:03 --- I don't think it's unreasonable for the servlet to control the HTTP connection - it is supported by both the s

DO NOT REPLY [Bug 30273] - The HTTP 1.1 processor ignores "Connection: close" on response

gzilla/show_bug.cgi?id=30273 The HTTP 1.1 processor ignores "Connection: close" on response [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW

DO NOT REPLY [Bug 30273] New: - The HTTP 1.1 processor ignores "Connection: close" on response

gzilla/show_bug.cgi?id=30273 The HTTP 1.1 processor ignores "Connection: close" on response Summary: The HTTP 1.1 processor ignores "Connection: close" on response Product: Tomcat 4 Version: 4.1.30 Platform: PC

DO NOT REPLY [Bug 29671] - Context don't start with multiple HTTP 1.1 connectors

gzilla/show_bug.cgi?id=29671 Context don't start with multiple HTTP 1.1 connectors [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW

Autoreply: DO NOT REPLY [Bug 29671] - Context don't start with multiple HTTP 1.1 connectors

You have received this email for one of two reasons. One is that you or someone with your email address in their address book is infected with an email virus, and this virus was emailed to me. The other reason could be that you legitimately tried to contact me through on

DO NOT REPLY [Bug 29671] - Context don't start with multiple HTTP 1.1 connectors

gzilla/show_bug.cgi?id=29671 Context don't start with multiple HTTP 1.1 connectors --- Additional Comments From [EMAIL PROTECTED] 2004-06-18 15:12 --- Further to my submission: I had a AccessLogValve in my server.xml at an ENGINE level as follows: I then removed this from the ser

Autoreply: DO NOT REPLY [Bug 29671] New: - Context don't start with multiple HTTP 1.1 connectors

You have received this email for one of two reasons. One is that you or someone with your email address in their address book is infected with an email virus, and this virus was emailed to me. The other reason could be that you legitimately tried to contact me through on

DO NOT REPLY [Bug 29671] New: - Context don't start with multiple HTTP 1.1 connectors

gzilla/show_bug.cgi?id=29671 Context don't start with multiple HTTP 1.1 connectors Summary: Context don't start with multiple HTTP 1.1 connectors Product: Tomcat 5 Version: 5.0.25 Platform: PC OS/Version: Windows NT/2K

Re: HTTP 1.1 Connector - Bye bye?

then by all means, get rid of it. Cause now we are only removing it from new releases of TC 5 and not TC4 Filip - Original Message - From: "Shapira, Yoav" <[EMAIL PROTECTED]> To: "Tomcat Developers List" <[EMAIL PROTECTED]> Sent: Wednesday, May 19, 200

RE: HTTP 1.1 Connector - Bye bye?

12:59 PM >To: Tomcat Developers List >Subject: Re: HTTP 1.1 Connector - Bye bye? > >It's been gone from j-t-catalina for quite awhile now, so this would be a >change to TC 4.1.x. Personally I think that removing this would be too big >of a change for a maintenance branch. H

Re: HTTP 1.1 Connector - Bye bye?

ion up to those people that are still interested in it ;-). - Original Message - From: "Shapira, Yoav" <[EMAIL PROTECTED]> To: "Tomcat Developers List" <[EMAIL PROTECTED]> Sent: Wednesday, May 19, 2004 9:24 AM Subject: HTTP 1.1 Connector - Bye bye? Hi, S

Re: HTTP 1.1 Connector - Bye bye?

From: "Shapira, Yoav" <[EMAIL PROTECTED]> | To: "Tomcat Developers List" <[EMAIL PROTECTED]> | Sent: Wednesday, May 19, 2004 11:34 AM | Subject: RE: HTTP 1.1 Connector - Bye bye? | | | | Hi, | | >IMHO Quite a few people seem to still use it. I'd be inclined to

RE: HTTP 1.1 Connector - Bye bye?

Hanik - Dev [mailto:[EMAIL PROTECTED] >Sent: Wednesday, May 19, 2004 12:42 PM >To: Tomcat Developers List >Subject: Re: HTTP 1.1 Connector - Bye bye? > >keep it in, > >Like my great grand father said, "If it aint broke, don't fix it" :) >- Original Mess

Re: HTTP 1.1 Connector - Bye bye?

keep it in, Like my great grand father said, "If it aint broke, don't fix it" :) - Original Message - From: "Shapira, Yoav" <[EMAIL PROTECTED]> To: "Tomcat Developers List" <[EMAIL PROTECTED]> Sent: Wednesday, May 19, 2004 11:34 AM Subject:

RE: HTTP 1.1 Connector - Bye bye?

Hi, >IMHO Quite a few people seem to still use it. I'd be inclined to remove it I don't mind keeping it in (it's zero effort to keep it in, nonzero effort to remove it), but I'd like evidence that people are using it. Do you have any recent posts or something to that effect? Yoav Shapira Thi

RE: HTTP 1.1 Connector - Bye bye?

nal Message- > From: Shapira, Yoav [mailto:[EMAIL PROTECTED] > Sent: 19 May 2004 17:24 > To: Tomcat Developers List > Subject: HTTP 1.1 Connector - Bye bye? > > > > Hi, > Should we bid adieu to the HTTP11 connector (the old, > non-Coyote one) at > some poi

HTTP 1.1 Connector - Bye bye?

Hi, Should we bid adieu to the HTTP11 connector (the old, non-Coyote one) at some point in the near future? It's been deprecated for a while, and given the default settings (Coyote) and active discouragement from using HTTP11 to user, I think it's safe to assume it's not being widely used. We can

DO NOT REPLY [Bug 26113] New: - server-noexamples.xml.config uses the depricated connector HTTP/1.1

gzilla/show_bug.cgi?id=26113 server-noexamples.xml.config uses the depricated connector HTTP/1.1 Summary: server-noexamples.xml.config uses the depricated connector HTTP/1.1 Product: Tomcat 4 Version: 4.1.29 Platform: PC OS/Version: W

DO NOT REPLY [Bug 24428] - Non compliance with http 1.1 rfc: 100 (Continue) response

gzilla/show_bug.cgi?id=24428 Non compliance with http 1.1 rfc: 100 (Continue) response [EMAIL PROTECTED] changed: What|Removed |Added Severity|Major |

DO NOT REPLY [Bug 24428] New: - Non compliance with http 1.1 rfc: 100 (Continue) response

gzilla/show_bug.cgi?id=24428 Non compliance with http 1.1 rfc: 100 (Continue) response Summary: Non compliance with http 1.1 rfc: 100 (Continue) response Product: Tomcat 4 Version: 4.1.27 Platform: PC OS/Version: Windows

Notes in HTTP 1.1 connectors

What about the idea to add notes in HTTP 1.1 connector ? It will mimic the way HTTPD teams using BrowserMatch : - Disable HTTP 1.0 for some browsers BrowserMatch "Mozilla/2" nokeepalive BrowserMatch "MSIE 4\.0b2;" nokeepalive downgrade-1.0 force-response-1.0 BrowserMatch &qu

DO NOT REPLY [Bug 9351] - IPv6 HTTP/1.1 requests not working

gzilla/show_bug.cgi?id=9351 IPv6 HTTP/1.1 requests not working [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Reso

DO NOT REPLY [Bug 17656] - scheme and secure Connector server.xml configuration attributes ignored by CoyoteConnector HTTP/1.1

gzilla/show_bug.cgi?id=17656 scheme and secure Connector server.xml configuration attributes ignored by CoyoteConnector HTTP/1.1 --- Additional Comments From [EMAIL PROTECTED] 2003-07-22 09:44 --- Maybe I misunderstood the comments, but it seems that the bug is still contained in version

DO NOT REPLY [Bug 17656] - scheme and secure Connector server.xml configuration attributes ignored by CoyoteConnector HTTP/1.1

gzilla/show_bug.cgi?id=17656 scheme and secure Connector server.xml configuration attributes ignored by CoyoteConnector HTTP/1.1 [EMAIL PROTECTED] changed: What|Removed |Added

DO NOT REPLY [Bug 17656] - scheme and secure Connector server.xml configuration attributes ignored by CoyoteConnector HTTP/1.1

gzilla/show_bug.cgi?id=17656 scheme and secure Connector server.xml configuration attributes ignored by CoyoteConnector HTTP/1.1 [EMAIL PROTECTED] changed: What|Removed |Added

DO NOT REPLY [Bug 17656] - scheme and secure Connector server.xml configuration attributes ignored by CoyoteConnector HTTP/1.1

gzilla/show_bug.cgi?id=17656 scheme and secure Connector server.xml configuration attributes ignored by CoyoteConnector HTTP/1.1 [EMAIL PROTECTED] changed: What|Removed |Added

DO NOT REPLY [Bug 17656] - scheme and secure Connector server.xml configuration attributes ignored by CoyoteConnector HTTP/1.1

gzilla/show_bug.cgi?id=17656 scheme and secure Connector server.xml configuration attributes ignored by CoyoteConnector HTTP/1.1 --- Additional Comments From [EMAIL PROTECTED] 2003-03-06 00:17 --- Created an attachment (id=5173) proposed patch, (tested on 4.1.18 ported f

DO NOT REPLY [Bug 17656] New: - scheme and secure Connector server.xml configuration attributes ignored by CoyoteConnector HTTP/1.1

gzilla/show_bug.cgi?id=17656 scheme and secure Connector server.xml configuration attributes ignored by CoyoteConnector HTTP/1.1 Summary: scheme and secure Connector server.xml configuration attributes ignored by CoyoteConnector HTTP/1.1 Product: To

DO NOT REPLY [Bug 15268] - SSLPeerUnverifiedException on every request when using SSL Coyote HTTP/1.1 Connector

gzilla/show_bug.cgi?id=15268 SSLPeerUnverifiedException on every request when using SSL Coyote HTTP/1.1 Connector [EMAIL PROTECTED] changed: What|Removed |Added Stat

DO NOT REPLY [Bug 15268] New: - SSLPeerUnverifiedException on every request when using SSL Coyote HTTP/1.1 Connector

gzilla/show_bug.cgi?id=15268 SSLPeerUnverifiedException on every request when using SSL Coyote HTTP/1.1 Connector Summary: SSLPeerUnverifiedException on every request when using SSL Coyote HTTP/1.1 Connector Product: Tomcat 4 Version:

DO NOT REPLY [Bug 13441] - WebApp Connector not writing status code properly on HTTP/1.1 responses

gzilla/show_bug.cgi?id=13441 WebApp Connector not writing status code properly on HTTP/1.1 responses [EMAIL PROTECTED] changed: What|Removed |Added Stat

DO NOT REPLY [Bug 13441] New: - WebApp Connector not writing status code properly on HTTP/1.1 responses

gzilla/show_bug.cgi?id=13441 WebApp Connector not writing status code properly on HTTP/1.1 responses Summary: WebApp Connector not writing status code properly on HTTP/1.1 responses Product: Tomcat 4 Version: 4.1.12 Platform:

DO NOT REPLY [Bug 9351] - IPv6 HTTP/1.1 requests not working

gzilla/show_bug.cgi?id=9351 IPv6 HTTP/1.1 requests not working --- Additional Comments From [EMAIL PROTECTED] 2002-05-23 17:18 --- I have developed no bug fix yet, but it shouldn't be very difficult to do it (it's a simple String parsing). As of now we're using a little worka

DO NOT REPLY [Bug 9351] - IPv6 HTTP/1.1 requests not working

gzilla/show_bug.cgi?id=9351 IPv6 HTTP/1.1 requests not working --- Additional Comments From [EMAIL PROTECTED] 2002-05-23 16:31 --- Can you submit a patch on that topic, of course tested with J2SE 1.4, to see if it actually works? A current workaround would be to use a host name resolving

DO NOT REPLY [Bug 9351] New: - IPv6 HTTP/1.1 requests not working

gzilla/show_bug.cgi?id=9351 IPv6 HTTP/1.1 requests not working Summary: IPv6 HTTP/1.1 requests not working Product: Tomcat 4 Version: 4.0.3 Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority:

DO NOT REPLY [Bug 6668] - HttpProcessor takes incorrect defaults for proxy port according to HTTP/1.1 Spec

gzilla/show_bug.cgi?id=6668 HttpProcessor takes incorrect defaults for proxy port according to HTTP/1.1 Spec [EMAIL PROTECTED] changed: What|Removed |Added

DO NOT REPLY [Bug 6668] - HttpProcessor takes incorrect defaults for proxy port according to HTTP/1.1 Spec

gzilla/show_bug.cgi?id=6668 HttpProcessor takes incorrect defaults for proxy port according to HTTP/1.1 Spec [EMAIL PROTECTED] changed: What|Removed |Added

DO NOT REPLY [Bug 6668] - HttpProcessor takes incorrect defaults for proxy port according to HTTP/1.1 Spec

gzilla/show_bug.cgi?id=6668 HttpProcessor takes incorrect defaults for proxy port according to HTTP/1.1 Spec [EMAIL PROTECTED] changed: What|Removed |Added

DO NOT REPLY [Bug 6668] - HttpProcessor takes incorrect defaults for proxy port according to HTTP/1.1 Spec

gzilla/show_bug.cgi?id=6668 HttpProcessor takes incorrect defaults for proxy port according to HTTP/1.1 Spec [EMAIL PROTECTED] changed: What|Removed |Added Stat

DO NOT REPLY [Bug 6450] - error-by-one in partial HTTP/1.1 GET requests

gzilla/show_bug.cgi?id=6450 error-by-one in partial HTTP/1.1 GET requests --- Additional Comments From [EMAIL PROTECTED] 2002-02-14 22:30 --- Thanks for your speedy reply! This fix is very gratifying! You've just become my short-duration-personal-saviour! -- To unsubscribe, e-mail

DO NOT REPLY [Bug 6450] - error-by-one in partial HTTP/1.1 GET requests

gzilla/show_bug.cgi?id=6450 error-by-one in partial HTTP/1.1 GET requests [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Com

DO NOT REPLY [Bug 6450] New: - error-by-one in partial HTTP/1.1 GET requests

gzilla/show_bug.cgi?id=6450 error-by-one in partial HTTP/1.1 GET requests Summary: error-by-one in partial HTTP/1.1 GET requests Product: Tomcat 4 Version: 4.0.1 Final Platform: PC URL: www.activesky.com OS/Version: Windows

Tomcat 4.0.1 and HTTP/1.1

All, I'm interested on the HTTP/1.1 implementation, however, I'm not sure if this has been implemented on both Tomcat 3.3 and Tomcat 4.0 or just 4.0. If it is implemented, does it support full HTTP/1.1 spec or not? If anyone knows the answer of this, please share it with me. Kinde

Re: HTTP/1.1

- Original Message - From: Artur Jonak <[EMAIL PROTECTED]> Hi, > > How to send response from my servlet with HTTP/1.1 header? > All responses have HTTP/1.0 headers. Can I change it? > > Regards, > AJ > HTTP connector in Tomcat 4.x talks HTTP 1.1. Are you

HTTP/1.1

Hi, How to send response from my servlet with HTTP/1.1 header? All responses have HTTP/1.0 headers. Can I change it? Regards, AJ Pozdrawiam, AJ. <mailto:[EMAIL PROTECTED]> <http://strony.wp.pl/wp/ajonak>

Re: HTTP 1.1 in Tomcat

Thanks for the encouragement, Costin. I'll give it a shot and let you know if I run into something I don't understand. [EMAIL PROTECTED] wrote: >On Mon, 14 May 2001, Bruce Butterfield wrote: > >>What would be the major issue of adding HTTP 1.1 capability to Tomcat &g

Re: HTTP 1.1 in Tomcat

On Mon, 14 May 2001, Bruce Butterfield wrote: > What would be the major issue of adding HTTP 1.1 capability to Tomcat > 3.2.x? Our application uses Tomcat standalone because there is almost no > static content and thus using the Apache server seems superfluous. We > expose SOAP-

HTTP 1.1 in Tomcat

What would be the major issue of adding HTTP 1.1 capability to Tomcat 3.2.x? Our application uses Tomcat standalone because there is almost no static content and thus using the Apache server seems superfluous. We expose SOAP-like APIs to the application and performance would certainly get a

Re: tomcat 4 http/1.1 connector and keep alives

> why does the http/1.1 connector in tomcat 4 not set a connection: > keep-alive header? doesn't it need to? No. Keepalive is HTTP/1.0. In 1.1 connections are kept alive by default. Remy

tomcat 4 http/1.1 connector and keep alives

why does the http/1.1 connector in tomcat 4 not set a connection: keep-alive header? doesn't it need to? thanks, -kevin

HTTP/1.1 Request lacking Host Header

According to the HTTP/1.1 RFC (section 14.23) all HTTP/1.1 requests MUST contain a Host header, and all HTTP/1.1 severs MUST respond with a 400 if the Host header is missing from an HTTP/1.1 request. Tomcat 4.0b3 responds with a '200 OK HTTP/1.1' response if I send a the foll