[TAPESTRY-685] Asset service sends a 200 response even when the provided md5 checksum is invalid

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 4.0
• Fix Version/s: 4.0
• Component/s: Framework
• Assignee: Howard Lewis Ship
• Reporter: Howard Lewis Ship
• Created: 03/Oct/05 23:39
• Updated: 09/Oct/05 01:02
• Resolved: 09/Oct/05 01:02

Description

Not exactly sure what the browsers do with this, but I'm beginning to suspect that this is the reason why strange JavaScript behavior occurs after a change to an asset ... the browser thinks it can continue to use the OLD file.

Here's some proof:

bash-3.00$ curl -I http://localhost:9090/assets/b4909c59529064c46eb8843b65911500/org/apache/tapestry/form/Form.js
HTTP/1.1 200 OK
Date: Mon, 03 Oct 2005 14:35:49 GMT
Server: Jetty/4.2.22 (Windows XP/5.1 x86 java/1.5.0_04)
Content-Length: 10652
Last-Modified: Mon, 03 Oct 2005 14:29:06 GMT
Expires: Thu, 20 Oct 2005 15:09:35 GMT
Content-Type: application/x-javascript

bash-3.00$ curl -I http://localhost:9090/assets/b4909c59529064c46eb8843b65911501/org/apache/tapestry/form/Form.js
HTTP/1.1 200 OK
Date: Mon, 03 Oct 2005 14:35:56 GMT
Server: Jetty/4.2.22 (Windows XP/5.1 x86 java/1.5.0_04)
Content-Length: 0

bash-3.00$

In the second command, the md5 checksum was bad, but it was still a 200 return code.