Asset service sends a 200 response even when the provided md5 checksum is
invalid
---------------------------------------------------------------------------------
Key: TAPESTRY-685
URL: http://issues.apache.org/jira/browse/TAPESTRY-685
Project: Tapestry
Type: Bug
Components: Framework
Versions: 4.0
Reporter: Howard M. Lewis Ship
Priority: Minor
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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
