X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-2.2 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Message-ID: <4B71B094.40202@etr-usa.com> Date: Tue, 09 Feb 2010 11:59:32 -0700 From: Warren Young User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.7) Gecko/20100111 Thunderbird/3.0.1 MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: Wrong setup.exe on http://www.cygwin.com/ References: <1265668504.29489.ezmlm@cygwin.com> <20100209164916.GB18306@ednor.casa.cgf.cx> <4B719B03.40309@etr-usa.com> <20100209180323.GA17500@ednor.casa.cgf.cx> <20100209180515.GB17500@ednor.casa.cgf.cx> In-Reply-To: <20100209180515.GB17500@ednor.casa.cgf.cx> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On 2/9/2010 11:05 AM, Christopher Faylor wrote: >> That should reduce cygwin mailing >> list traffic at the expense of network traffic on cygwin.com I doubt it'll make a significant difference. Browser caches turn over pretty regularly, so between any two visits, the chance that there is still a copy of setup.exe and it's still current is pretty low. Browser caches matter more for resources needed on every visit, especially those shared between multiple pages on that site. (cygwin.jpg, for instance.) I'd bet the ratio of setup.exe downloads to site hits is below 0.5. Maybe even below 0.1. You might check that web spiders don't download setup.exe. If they do, I'd block them from it with robots.txt. > Btw, I did check the difference in http headers in the before/after > scenario and now see a new "Expires" field but I have no way of actually > checking this to see if it really does solve a problem. The Net panel in the Firebug extension for Firefox can do this. And indeed, it looks like you haven't fully defeated caching yet. On a cleaned cache, I get an HTTP 200 response code for setup.exe, but 304 (Not Modified) thereafter. If the cache were defeated, it would be 200 every time. Assuming you have fully restarted Apache, the next thing to try is: FileETag none Incidentally, while poking around with this, I ran into a spate of validation errors on the home page. One particularly ugly one is a second tag on line 261 of the home page. The best way I know of to clean up things like this is with the Html Validator Firefox extension: https://addons.mozilla.org/en-US/firefox/addon/249 After you install it, the View Source window is augmented to do validation, with an error list coupled to the source listing, much like the way code IDEs tie compiler errors to source lines. Because it's right there in your browser and runs client-side, you get real-time feedback about the cleanliness of your code as you work on the page. Unlike other free validation services, you don't have to publish the page for all to see before you can validate. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple