tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 38546] New: - Google bot sends invalid If-Modifed-Since Header, Tomcat throws exception
Date Tue, 07 Feb 2006 03:15:04 GMT
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=38546>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=38546

           Summary: Google bot sends invalid If-Modifed-Since Header, Tomcat
                    throws exception
           Product: Tomcat 5
           Version: 5.0.28
          Platform: Other
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Catalina
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: rick@knowleses.org


Not sure if this is fixed in the recent versions, or even if it should be, but 
thought it should be noted somewhere. Feel free to close this as invalid, 
since it isn't tomcat's fault. 

When being crawled by the google bot (User-Agent: Mozilla/5.0 (compatible; 
Googlebot/2.1; +http://www.google.com/bot.html)) the following exception gets 
thrown on each of the servlets I've deployed that implement the getLastModified
() call.

java.lang.IllegalArgumentException: Mon, 06 Feb 2006 17:14:33
	at org.apache.coyote.tomcat5.CoyoteRequest.getDateHeader
(CoyoteRequest.java:1887)
	at org.apache.coyote.tomcat5.CoyoteRequestFacade.getDateHeader
(CoyoteRequestFacade.java:426)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:691)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter
(ApplicationFilterChain.java:237)

I'm pretty sure the error is Google's. The RFC requires a timezone to be 
appended for date headers (and more specfically a GMT timezone), which this 
one doesn't have. 

Would it be possible to have tomcat simply throw a warning here ? It is a 
recoverable error if we assumed the timezone was GMT if omitted, and logged as 
an invalid timestamp ? Or possibly even trapped, logged as a warning and 
assumed to be not supplied (i.e. = 1970).

I understand this is probably not a tomcat bug, and I will lodge it with the 
Google bot support as well, but wondered whether it might not be a good 
robustness thing to add in anyway.

-- 
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 the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org


Mime
View raw message