Bug report #620 has just been filed. You can view the report at the following URL: <http://znutar.cortexity.com/BugRatViewer/ShowReport/620> REPORT #620 Details. Project: Tomcat Category: Bug Report SubCategory: New Bug Report Class: swbug State: received Priority: medium Severity: non-critical Confidence: public Environment: Release: 3.2 JVM Release: 1.3.0 Operating System: Solaris OS Release: 7 Platform: Sparc Synopsis: getProtocol() method on ServletRequest includes CRLF causing problems Description: In Tomcat 3.2.0 the getProtocol() method on a ServletRequest includes CRLF (0x0d 0x0a) in the return value. Logic relying on string comparison like getProtocol().equals("HTTP/1.0") won't work anymore. The problem is in the HttpAdapter.parseHeaderFiled() method, that makes use of the BuffTool class for parsing the request headers. A quick solution would be to change the source to: req.setProtocol( new String( buf, startProto, endProto-startProto ).trim());Title: BugRat Report # 620
BugRat Report # 620
| Project: Tomcat | Release: 3.2 |
| Category: Bug Report | SubCategory: New Bug Report |
| Class: swbug | State: received |
| Priority: medium | Severity: non-critical |
|
Confidence:
public
|
Submitter:
Mark Brouwer ( [EMAIL PROTECTED] )
Date Submitted:
Dec 19 2000, 08:22:43 CST
Responsible:
Z_Tomcat Alias ( [EMAIL PROTECTED] )
- Synopsis:
- getProtocol() method on ServletRequest includes CRLF causing problems
- Environment: (jvm, os, osrel, platform)
- 1.3.0, Solaris, 7, Sparc
- Additional Environment Description:
- Report Description:
- In Tomcat 3.2.0 the getProtocol() method on a ServletRequest includes CRLF (0x0d 0x0a) in the return value. Logic relying on string comparison like getProtocol().equals("HTTP/1.0") won't work anymore. The problem is in the HttpAdapter.parseHeaderFiled() method, that makes use of the BuffTool class for parsing the request headers. A quick solution would be to change the source to: req.setProtocol( new String( buf, startProto, endProto-startProto ).trim());
- Workaround:
- null
