Return-Path: Delivered-To: apmail-jakarta-tapestry-dev-archive@www.apache.org Received: (qmail 30163 invoked from network); 8 Oct 2005 16:04:19 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 8 Oct 2005 16:04:19 -0000 Received: (qmail 15035 invoked by uid 500); 8 Oct 2005 16:04:15 -0000 Delivered-To: apmail-jakarta-tapestry-dev-archive@jakarta.apache.org Received: (qmail 14912 invoked by uid 500); 8 Oct 2005 16:04:14 -0000 Mailing-List: contact tapestry-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Tapestry development" Reply-To: "Tapestry development" Delivered-To: mailing list tapestry-dev@jakarta.apache.org Received: (qmail 14864 invoked by uid 99); 8 Oct 2005 16:04:14 -0000 X-ASF-Spam-Status: No, hits=0.5 required=10.0 tests=SPF_FAIL,WEIRD_PORT X-Spam-Check-By: apache.org Received: from [192.87.106.226] (HELO ajax.apache.org) (192.87.106.226) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 08 Oct 2005 09:04:12 -0700 Received: from ajax.apache.org (ajax.apache.org [127.0.0.1]) by ajax.apache.org (Postfix) with ESMTP id 19E32224 for ; Sat, 8 Oct 2005 18:03:51 +0200 (CEST) Message-ID: <171152533.1128787431104.JavaMail.jira@ajax.apache.org> Date: Sat, 8 Oct 2005 18:03:51 +0200 (CEST) From: "Howard M. Lewis Ship (JIRA)" To: tapestry-dev@jakarta.apache.org Subject: [jira] Closed: (TAPESTRY-685) Asset service sends a 200 response even when the provided md5 checksum is invalid In-Reply-To: <629043927.1128350387972.JavaMail.jira@ajax.apache.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N [ http://issues.apache.org/jira/browse/TAPESTRY-685?page=all ] Howard M. Lewis Ship closed TAPESTRY-685: ----------------------------------------- Fix Version: 4.0 Resolution: Fixed Assign To: Howard M. Lewis Ship Now sends a 403 status code and a error message: bash-3.00$ curl -D - http://localhost:8080/assets/b4909c59529064c46eb8843b65911500x/org/apache/tapestry/form/Form.js HTTP/1.1 403 The+MD5+digest+provided+in+the+request+does+not+match+the+actual+value+for+classpath+resource+%27%2Forg%2Fapache%2Ftapestry%2Fform%2FForm%2Ejs%27%2E Date: Sat, 08 Oct 2005 16:00:16 GMT Server: Jetty/4.2.22 (Windows XP/5.1 x86 java/1.5.0_04) Content-Type: text/html Content-Length: 1554 Error 403 The+MD5+digest+provided+in+the+request+does+not+match+the+actual+value+for+classpath+resource+%27%2Forg%2Fapache%2Ftapestry%2Fform%2FForm%2Ejs%27%2E

HTTP ERROR: 403 The+MD5+digest+provided+in+the+request+does+not+match+the+actual+value+for+classpath+resource+%27%2Forg%2Fapache%2Ftapestry%2Fform%2FForm%2Ejs%27%2E

RequestURI=/assets/b4909c59529064c46eb8843b65911500x/org/apache/tapestry/form/Form.js

Powered by Jetty://

bash-3.00$ > 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 > Assignee: Howard M. Lewis Ship > Priority: Minor > Fix For: 4.0 > > 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: tapestry-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org