Jakub Narebski wrote:The CGI spec does not at all guarantee that the CGI environment will contain all the HTTP headers sent by the client. That was the point of the environment dump script -- you can see exactly which headers are, and are not, passed through to CGI. CGI only /guarantees/ a bare minimum (things like QUERY_STRING, PATH_INFO, etc.) Even basic server info environment variables are optional. It's not meant to output the sample file. It outputs the server metadata sent to the CGI script (the environment variables). The sample file was simply a way to play around with etag and last-modified metadata. Certainly. That should help cut down on I/O. FWIW though the projects list is particularly painful, with its File::Find call, which you'll need to do in order to return 304-not-modified. This wanders into the realm of mod_cache configuration, I think. (which I have tried to get working as reverse proxy, and failed serveral times) If you are not using mod_*_cache, then Apache must execute the CGI script every time AFAICS, regardless of etag/[if-]last-mod headers. Jeff - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Greg Kroah-Hartman | [PATCH 005/196] Chinese: add translation of SubmittingDrivers |
| Andy Whitcroft | Re: 2.6.21-rc7-mm2 -- x86_64 blade hard hangs |
| Rafael J. Wysocki | 2.6.26-rc1-git9: Reported regressions from 2.6.25 |
git: | |
| Andy Grover | [PATCH 01/21] RDS: Socket interface |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| David Miller | [GIT]: Networking |
| Gerrit Renker | [PATCH 03/37] dccp: List management for new feature negotiation |
