Summary: | Filename/info for disk-cached proxied remote URLs not available. | ||
---|---|---|---|
Product: | Apache httpd-2 | Reporter: | D. Stussy <software+apache-httpd> |
Component: | mod_cache | Assignee: | Apache HTTPD Bugs Mailing List <bugs> |
Status: | RESOLVED LATER | ||
Severity: | enhancement | CC: | software+apache-httpd |
Priority: | P4 | Keywords: | MassUpdate |
Version: | 2.2.4 | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Linux |
Description
D. Stussy
2007-05-13 12:32:20 UTC
The problem with gaining access to a file is that the file only makes sense if there is a single file, and in the case of the disk cache, there are multiple separate files that represent the body of each variant, and the headers of each variant. A better approach would be to expose a more formal API to query the status of cached URLs. htcacheclean in httpd-trunk how has the ability to list entries in the cache (-a flag), and list entries in the cache along with a complete dump of cached metadata (-A flag). Will this be enough? RE - Comment #1: I am aware that the cache generates two files (header and body) per request cached, and additional files when the request varies. The file would be the body file returned according to the headers given in the subrequest after variance is applied. This reduces the subrequest to a single file, if one exists. If one does not exist, then "proxy:URL" (or other appropriate substitute string) that is currently returned will still be returned. Clarification: The concept is akin to the ability to retrieve the last cached copy of a resource like certain search engines keep around (e.g. google). RE - Comment #2: No. My idea concerned making the local filename (from the cache when the URL is remote) available to the HTTP request itself (as a subrequest if appropriate). Therefore, availability to the htcacheclean program does not help. (However, it may be helpful for maintenance purposes.) Does that make more sense about what I am suggesting? Please help us to refine our list of open and current defects; this is a mass update of old and inactive Bugzilla reports which reflect user error, already resolved defects, and still-existing defects in httpd. As repeatedly announced, the Apache HTTP Server Project has discontinued all development and patch review of the 2.2.x series of releases. The final release 2.2.34 was published in July 2017, and no further evaluation of bug reports or security risks will be considered or published for 2.2.x releases. All reports older than 2.4.x have been updated to status RESOLVED/LATER; no further action is expected unless the report still applies to a current version of httpd. If your report represented a question or confusion about how to use an httpd feature, an unexpected server behavior, problems building or installing httpd, or working with an external component (a third party module, browser etc.) we ask you to start by bringing your question to the User Support and Discussion mailing list, see [https://httpd.apache.org/lists.html#http-users] for details. Include a link to this Bugzilla report for completeness with your question. If your report was clearly a defect in httpd or a feature request, we ask that you retest using a modern httpd release (2.4.33 or later) released in the past year. If it can be reproduced, please reopen this bug and change the Version field above to the httpd version you have reconfirmed with. Your help in identifying defects or enhancements still applicable to the current httpd server software release is greatly appreciated. |