[Bug 53281] Tomcat returns garbage data with HTTP/0.9 200 OK header when SSL port is accessed using http
https://issues.apache.org/bugzilla/show_bug.cgi?id=53281 --- Comment #18 from xudong.liu xu-dong@sap.com --- I meet the same issue in my test. I want to know if this issue can be fixed? Why it's status is marked invalid? -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[Bug 53281] Tomcat returns garbage data with HTTP/0.9 200 OK header when SSL port is accessed using http
https://issues.apache.org/bugzilla/show_bug.cgi?id=53281 --- Comment #17 from saurabh saurabhsul...@yahoo.co.in --- (In reply to Konstantin Preißer from comment #14) (In reply to saurabh from comment #12) Created attachment 30912 [details] HTTP 0.9 response from the server I tried the identical steps that have been provided and the browser receives garbage value with HTTP/0.9 response. I've attached the Live HTTP headers capture of the same. Just because some Browser Add-on reports a HTTP/0.9 200 OK response it doesn't necessarily mean that this is what Tomcat is actually sending (otherwise you should have seen that response when you are connecting with telnet. My guess would be that the add-on (or even the browser) is trying to interpret SSL bytes as plain HTTP response, and because it fails, displayes some HTTP/0.9 response. I verified this by setting up Tomcat 6.0.37 with a SSL connector using JSSE, and downloadeding the Live HTTP headers addon for Firefox. I use a tool to intercept the TCP connections and record the exact data packets that were sent. I then opened the URL http://localhost:8443/; with Firefox. This is what was sent from Firefox to Tomcat (309 bytes): 47 45 54 20 2F 20 48 54 54 50 2F 31 2E 31 0D 0A GET / HTTP/1.1.. 48 6F 73 74 3A 20 6C 6F 63 61 6C 68 6F 73 74 3A Host: localhost: 38 34 34 33 0D 0A 55 73 65 72 2D 41 67 65 6E 74 8443..User-Agent 3A 20 4D 6F 7A 69 6C 6C 61 2F 35 2E 30 20 28 57 : Mozilla/5.0 (W 69 6E 64 6F 77 73 20 4E 54 20 36 2E 33 3B 20 57 indows NT 6.3; W 4F 57 36 34 3B 20 72 76 3A 32 34 2E 30 29 20 47 OW64; rv:24.0) G 65 63 6B 6F 2F 32 30 31 30 30 31 30 31 20 46 69 ecko/20100101 Fi 72 65 66 6F 78 2F 32 34 2E 30 0D 0A 41 63 63 65 refox/24.0..Acce 70 74 3A 20 74 65 78 74 2F 68 74 6D 6C 2C 61 70 pt: text/html,ap 70 6C 69 63 61 74 69 6F 6E 2F 78 68 74 6D 6C 2B plication/xhtml+ 78 6D 6C 2C 61 70 70 6C 69 63 61 74 69 6F 6E 2F xml,application/ 78 6D 6C 3B 71 3D 30 2E 39 2C 2A 2F 2A 3B 71 3D xml;q=0.9,*/*;q= 30 2E 38 0D 0A 41 63 63 65 70 74 2D 4C 61 6E 67 0.8..Accept-Lang 75 61 67 65 3A 20 64 65 2D 64 65 2C 64 65 3B 71 uage: de-de,de;q 3D 30 2E 38 2C 65 6E 2D 75 73 3B 71 3D 30 2E 35 =0.8,en-us;q=0.5 2C 65 6E 3B 71 3D 30 2E 33 0D 0A 41 63 63 65 70 ,en;q=0.3..Accep 74 2D 45 6E 63 6F 64 69 6E 67 3A 20 67 7A 69 70 t-Encoding: gzip 2C 20 64 65 66 6C 61 74 65 0D 0A 43 6F 6E 6E 65 , deflate..Conne 63 74 69 6F 6E 3A 20 6B 65 65 70 2D 61 6C 69 76 ction: keep-aliv 65 0D 0A 0D 0Ae This is what Tomcat responded (7 bytes): 15 03 01 00 02 02 0A ... (Connection closed) This is what Live HTTP headers reported: http://localhost:8443/ GET / HTTP/1.1 Host: localhost:8443 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Firefox/24.0 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Accept-Language: de-de,de;q=0.8,en-us;q=0.5,en;q=0.3 Accept-Encoding: gzip, deflate Connection: keep-alive HTTP/0.9 200 OK -- As you can see, Tomcat didn't returin anything like HTTP/0.9 200 OK plain text in its SSL response although Live HTTP Headers reports this. Instead it sends some some SSL reply (though I do not have examined what kind of reply it is), since actually you are sending some garbage to a SSL connector here. If Tomcat could be enhanced to recognize a erroneously sent plain HTTP request to a HTTPS/SSL connector (like HTTPD does) is another question. I tried to figure out the SSL bytes -- 15 03 01 00 02 02 0A using the following link: http://pic.dhe.ibm.com/infocenter/tpfhelp/current/index.jsp?topic=%2Fcom.ibm.ztpf-ztpfdf.doc_put.cur%2Fgtps5%2Fs5rcd.html This is what I think those bytes mean: 0x15 -- SSL3_RT_ALERT 0x03 0x01 -- TLS1_VERSION 0x00 0x02 -- Length of data in the record (excluding the header itself) 0x02 -- SSL3_MT_SERVER_HELLO or SSL3_AL_FATAL 0x0A -- SSL3_AD_UNEXPECTED_MESSAGE -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[Bug 53281] Tomcat returns garbage data with HTTP/0.9 200 OK header when SSL port is accessed using http
https://issues.apache.org/bugzilla/show_bug.cgi?id=53281 --- Comment #12 from saurabh saurabhsul...@yahoo.co.in --- Created attachment 30912 -- https://issues.apache.org/bugzilla/attachment.cgi?id=30912action=edit HTTP 0.9 response from the server I tried the identical steps that have been provided and the browser receives garbage value with HTTP/0.9 response. I've attached the Live HTTP headers capture of the same. I've also tried using curl and telnet as indicated in the comments above. Here is the output of both the commands: [root@host ~]# curl -f http://myhost:9876 -- blank line Note: the blank line means the server is returning some response. Not the same as has been indicated in the comments above. [root@host ~]# telnet myhost 9876 Trying 10.10.10.1... Connected to myhost (10.10.10.1). Escape character is '^]'. GET / HTTP/1.1 Connection closed by foreign host. So, I tried running tcpdump to take the captures for all the three ways of accessing the server namely Browser, Curl and Telnet and in each capture I saw a response being received from the server. Note: I'm using Firefox as the Browser but the behavior is consistent with IE as well. Note: I'm using JSSE with Tomcat for the SSL. -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[Bug 53281] Tomcat returns garbage data with HTTP/0.9 200 OK header when SSL port is accessed using http
https://issues.apache.org/bugzilla/show_bug.cgi?id=53281 --- Comment #13 from robchek robc...@knowledgetree.com --- (In reply to Mark Thomas from comment #11) Tested with 6.0.x and confirmed that: - connecting to the https port using http with a browser returns garbage (as expected) - connecting to the https port with telnet and sending a valid HTTP request list results in garbage being returned and the connection closed (as expected) - at no point is an HTTP/0.9 response line returned Just want to articulate that it seems that there are 2 issues in play here: 1. garbage data: I think this is the intent of the original posting; that Tomcat should not return garbage data, but instead return code 400 similar to Apache behavior. 2. HTTP/0.9 response returned: I have not seen this aspect. -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[Bug 53281] Tomcat returns garbage data with HTTP/0.9 200 OK header when SSL port is accessed using http
https://issues.apache.org/bugzilla/show_bug.cgi?id=53281 --- Comment #14 from Konstantin Preißer kpreis...@apache.org --- (In reply to saurabh from comment #12) Created attachment 30912 [details] HTTP 0.9 response from the server I tried the identical steps that have been provided and the browser receives garbage value with HTTP/0.9 response. I've attached the Live HTTP headers capture of the same. Just because some Browser Add-on reports a HTTP/0.9 200 OK response it doesn't necessarily mean that this is what Tomcat is actually sending (otherwise you should have seen that response when you are connecting with telnet. My guess would be that the add-on (or even the browser) is trying to interpret SSL bytes as plain HTTP response, and because it fails, displayes some HTTP/0.9 response. I verified this by setting up Tomcat 6.0.37 with a SSL connector using JSSE, and downloadeding the Live HTTP headers addon for Firefox. I use a tool to intercept the TCP connections and record the exact data packets that were sent. I then opened the URL http://localhost:8443/; with Firefox. This is what was sent from Firefox to Tomcat (309 bytes): 47 45 54 20 2F 20 48 54 54 50 2F 31 2E 31 0D 0A GET / HTTP/1.1.. 48 6F 73 74 3A 20 6C 6F 63 61 6C 68 6F 73 74 3A Host: localhost: 38 34 34 33 0D 0A 55 73 65 72 2D 41 67 65 6E 74 8443..User-Agent 3A 20 4D 6F 7A 69 6C 6C 61 2F 35 2E 30 20 28 57 : Mozilla/5.0 (W 69 6E 64 6F 77 73 20 4E 54 20 36 2E 33 3B 20 57 indows NT 6.3; W 4F 57 36 34 3B 20 72 76 3A 32 34 2E 30 29 20 47 OW64; rv:24.0) G 65 63 6B 6F 2F 32 30 31 30 30 31 30 31 20 46 69 ecko/20100101 Fi 72 65 66 6F 78 2F 32 34 2E 30 0D 0A 41 63 63 65 refox/24.0..Acce 70 74 3A 20 74 65 78 74 2F 68 74 6D 6C 2C 61 70 pt: text/html,ap 70 6C 69 63 61 74 69 6F 6E 2F 78 68 74 6D 6C 2B plication/xhtml+ 78 6D 6C 2C 61 70 70 6C 69 63 61 74 69 6F 6E 2F xml,application/ 78 6D 6C 3B 71 3D 30 2E 39 2C 2A 2F 2A 3B 71 3D xml;q=0.9,*/*;q= 30 2E 38 0D 0A 41 63 63 65 70 74 2D 4C 61 6E 67 0.8..Accept-Lang 75 61 67 65 3A 20 64 65 2D 64 65 2C 64 65 3B 71 uage: de-de,de;q 3D 30 2E 38 2C 65 6E 2D 75 73 3B 71 3D 30 2E 35 =0.8,en-us;q=0.5 2C 65 6E 3B 71 3D 30 2E 33 0D 0A 41 63 63 65 70 ,en;q=0.3..Accep 74 2D 45 6E 63 6F 64 69 6E 67 3A 20 67 7A 69 70 t-Encoding: gzip 2C 20 64 65 66 6C 61 74 65 0D 0A 43 6F 6E 6E 65 , deflate..Conne 63 74 69 6F 6E 3A 20 6B 65 65 70 2D 61 6C 69 76 ction: keep-aliv 65 0D 0A 0D 0Ae This is what Tomcat responded (7 bytes): 15 03 01 00 02 02 0A ... (Connection closed) This is what Live HTTP headers reported: http://localhost:8443/ GET / HTTP/1.1 Host: localhost:8443 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Firefox/24.0 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Accept-Language: de-de,de;q=0.8,en-us;q=0.5,en;q=0.3 Accept-Encoding: gzip, deflate Connection: keep-alive HTTP/0.9 200 OK -- As you can see, Tomcat didn't returin anything like HTTP/0.9 200 OK plain text in its SSL response although Live HTTP Headers reports this. Instead it sends some some SSL reply (though I do not have examined what kind of reply it is), since actually you are sending some garbage to a SSL connector here. If Tomcat could be enhanced to recognize a erroneously sent plain HTTP request to a HTTPS/SSL connector (like HTTPD does) is another question. -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[Bug 53281] Tomcat returns garbage data with HTTP/0.9 200 OK header when SSL port is accessed using http
https://issues.apache.org/bugzilla/show_bug.cgi?id=53281 --- Comment #15 from Mark Thomas ma...@apache.org --- (In reply to Konstantin Preißer from comment #14) As you can see, Tomcat didn't returin anything like HTTP/0.9 200 OK plain text in its SSL response although Live HTTP Headers reports this. Instead it sends some some SSL reply (though I do not have examined what kind of reply it is), since actually you are sending some garbage to a SSL connector here. It should be the start of the SSL handshake. If Tomcat could be enhanced to recognize a erroneously sent plain HTTP request to a HTTPS/SSL connector (like HTTPD does) is another question. It can't. -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[Bug 53281] Tomcat returns garbage data with HTTP/0.9 200 OK header when SSL port is accessed using http
https://issues.apache.org/bugzilla/show_bug.cgi?id=53281 --- Comment #16 from Christopher Schultz ch...@christopherschultz.net --- Mark, can you comment on why Tomcat is limited further than, say, httpd? I think that might help drive the final nail in the coffin, here. Is the problem that the Java SSL layer is so far below what Tomcat controls that catching an invalid client HELLO before the Java SSL layer replies is not possible? -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[Bug 53281] Tomcat returns garbage data with HTTP/0.9 200 OK header when SSL port is accessed using http
https://issues.apache.org/bugzilla/show_bug.cgi?id=53281 robc...@knowledgetree.com changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|INVALID |--- --- Comment #9 from robc...@knowledgetree.com --- With Tomcat 6.0.37, it it straightforward to reproduce this issue using the following Connector (redacted): Connector port=9876 protocol=HTTP/1.1 SSLEnabled=true maxThreads=150 scheme=https secure=true keyAlias=mykey keystorePass=mypass clientAuth=false sslProtocol=TLS / $ curl -f http://www.myhost.com:9876 garbage returned -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[Bug 53281] Tomcat returns garbage data with HTTP/0.9 200 OK header when SSL port is accessed using http
https://issues.apache.org/bugzilla/show_bug.cgi?id=53281 robc...@knowledgetree.com changed: What|Removed |Added CC||robc...@knowledgetree.com -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[Bug 53281] Tomcat returns garbage data with HTTP/0.9 200 OK header when SSL port is accessed using http
https://issues.apache.org/bugzilla/show_bug.cgi?id=53281 --- Comment #10 from Christopher Schultz ch...@christopherschultz.net --- Note that I tested this with Tomcat 8 trunk. $ keytool -genkey -alias tomcat -keystore ~/.keystore -keyalg RSA -keysize 4096 Enter keystore password: Re-enter new password: What is your first and last name? [Unknown]: Christopher Schultz What is the name of your organizational unit? [Unknown]: Testing What is the name of your organization? [Unknown]: Snake Oil, Ltd. What is the name of your City or Locality? [Unknown]: Washington What is the name of your State or Province? [Unknown]: District of Columbia What is the two-letter country code for this unit? [Unknown]: US Is CN=Christopher Schultz, OU=Testing, O=Snake Oil, Ltd., L=Washington, ST=District of Columbia, C=US correct? [no]: yes Enter key password for tomcat (RETURN if same as keystore password): [left blank] I Modified your Connector slightly to match the key alias from the Tomcat documentation: Connector port=9876 protocol=HTTP/1.1 SSLEnabled=true maxThreads=150 scheme=https secure=true keyAlias=tomcat keystorePass=mypass clientAuth=false sslProtocol=TLS / $ curl -f http://localhost:9876 curl: (52) Empty reply from server $ telnet localhost 9876 Trying ::1... Connected to localhost. Escape character is '^]'. GET / Connection closed by foreign host. $ telnet localhost 9876 Trying ::1... Connected to localhost. Escape character is '^]'. GET / HTTP/1.1 Connection closed by foreign host. Tomcat is behaving as expected, here. I can test against Tomcat 6 to help corroborate, but I want to make sure that I have my process correct. To those who have reported problems, please verify that my steps-to-reproduce are correct. -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[Bug 53281] Tomcat returns garbage data with HTTP/0.9 200 OK header when SSL port is accessed using http
https://issues.apache.org/bugzilla/show_bug.cgi?id=53281 Mark Thomas ma...@apache.org changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |INVALID --- Comment #11 from Mark Thomas ma...@apache.org --- Tested with 6.0.x and confirmed that: - connecting to the https port using http with a browser returns garbage (as expected) - connecting to the https port with telnet and sending a valid HTTP request list results in garbage being returned and the connection closed (as expected) - at no point is an HTTP/0.9 response line returned My comment #1 from over a year ago stands. -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[Bug 53281] Tomcat returns garbage data with HTTP/0.9 200 OK header when SSL port is accessed using http
https://issues.apache.org/bugzilla/show_bug.cgi?id=53281 Bruce Li wbing...@gmail.com changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|INVALID |--- --- Comment #7 from Bruce Li wbing...@gmail.com --- Why is it resolved as invalid? Is there any solution to this issue? -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[Bug 53281] Tomcat returns garbage data with HTTP/0.9 200 OK header when SSL port is accessed using http
https://issues.apache.org/bugzilla/show_bug.cgi?id=53281 Konstantin Kolinko knst.koli...@gmail.com changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |INVALID --- Comment #8 from Konstantin Kolinko knst.koli...@gmail.com --- There are several reasons. The first one is that one has to prove that there is an issue. So far nobody reproduced this issue. Tomcat connectors do not behave as the OP describes. -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[Bug 53281] Tomcat returns garbage data with HTTP/0.9 200 OK header when SSL port is accessed using http
https://issues.apache.org/bugzilla/show_bug.cgi?id=53281 --- Comment #4 from Christopher Schultz ch...@christopherschultz.net --- My question isn't whether Tomcat can be configured to do that (it cannot currently do it), but if JSSE will even allow that handling to occur. If JSSE can't do it, Tomcat certainly can't do it using JSSE. -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[Bug 53281] Tomcat returns garbage data with HTTP/0.9 200 OK header when SSL port is accessed using http
https://issues.apache.org/bugzilla/show_bug.cgi?id=53281 --- Comment #5 from saurabh saurabhsul...@yahoo.co.in --- @Christopher Schultz - So if I understand you correctly, the issues lies with JSSE and not Tomcat, may I right? And that, there is no way we can change the behavior using Tomcat Configuration ? -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[Bug 53281] Tomcat returns garbage data with HTTP/0.9 200 OK header when SSL port is accessed using http
https://issues.apache.org/bugzilla/show_bug.cgi?id=53281 --- Comment #6 from Christopher Schultz ch...@christopherschultz.net --- No, I'm not saying that the issue is JSSE (though it may be). What I'm saying is that responding to an HTTP request over HTTPS is not impossible under all circumstances: httpd is an example of how it is possible. -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[Bug 53281] Tomcat returns garbage data with HTTP/0.9 200 OK header when SSL port is accessed using http
https://issues.apache.org/bugzilla/show_bug.cgi?id=53281 --- Comment #2 from Christopher Schultz ch...@christopherschultz.net --- Apache httpd does do something like this; not sure if it's possible using JSSE: $ telnet my.secure.site.com 443 Trying 208.85.173.131... Connected to my.secure.site.com. Escape character is '^]'. GET / blah !DOCTYPE HTML PUBLIC -//IETF//DTD HTML 2.0//EN htmlhead title400 Bad Request/title /headbody h1Bad Request/h1 pYour browser sent a request that this server could not understand.br / Reason: You're speaking plain HTTP to an SSL-enabled server port.br / Instead use the HTTPS scheme to access this URL, please.br / blockquoteHint: a href=https://my.secure.site.com/;bhttps://my.secure.site.com//b/a/blockquote/p hr addressApache/2.2 Server at my.secure.site.com Port 443/address /body/html Connection closed by foreign host. -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[Bug 53281] Tomcat returns garbage data with HTTP/0.9 200 OK header when SSL port is accessed using http
https://issues.apache.org/bugzilla/show_bug.cgi?id=53281 --- Comment #3 from saurabh saurabhsul...@yahoo.co.in --- Yes, Apache httpd does that. But I haven't been able to produce the same behavior using JSSE in Apache Tomcat. -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[Bug 53281] Tomcat returns garbage data with HTTP/0.9 200 OK header when SSL port is accessed using http
https://issues.apache.org/bugzilla/show_bug.cgi?id=53281 Mark Thomas ma...@apache.org changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #1 from Mark Thomas ma...@apache.org --- This is simply not possible if the SSL connector is correctly configured. Please use the users mailing list to identify your configuration error. -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[Bug 53281] Tomcat returns garbage data with HTTP/0.9 200 OK header when SSL port is accessed using http
https://issues.apache.org/bugzilla/show_bug.cgi?id=53281 saurabh saurabhsul...@yahoo.co.in changed: What|Removed |Added CC||saurabhsul...@yahoo.co.in -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
