Printable View
We've just finished a site with a currency RSS feed. The feed has been running without problems for about 6 weeks - then, as Murphy would have it, it screws up a day after launch.
This is the error message:
Can someone please help me?Code:Unable to open RSS Feed ansuz.sooke.bc.ca/rippy/exchange/?M=R&B=ZAR&F=USD,EUR,GBP&T=B&S=O&I=L with error HTTP ERROR: 304, exiting
Thanks
HTTP Error 304 Not ModifiedLooks like the content hasn't been updated and the application sending the request should use it's cached copyQuote:
If the client has performed a conditional GET request and access is allowed, but the document has not been modified, the server SHOULD respond with this status code. The 304 response MUST NOT contain a message-body, and thus is always terminated by the first empty line after the header fields.
The response MUST include the following header fields:
- Date, unless its omission is required by section 14.18.1
If a clockless origin server obeys these rules, and proxies and clients add their own Date to any response received without one (as already specified by [RFC 2068], section 14.19), caches will operate correctly.
- ETag and/or Content-Location, if the header would have been sent
in a 200 response to the same request
- Expires, Cache-Control, and/or Vary, if the field-value might
differ from that sent in any previous response for the same
variant
If the conditional GET used a strong cache validator (see section 13.3.3), the response SHOULD NOT include other entity-headers. Otherwise (i.e., the conditional GET used a weak validator), the response MUST NOT include other entity-headers; this prevents inconsistencies between cached entity-bodies and updated headers.
If a 304 response indicates an entity not currently cached, then the cache MUST disregard the response and repeat the request without the conditional.
If a cache uses a received 304 response to update a cache entry, the cache MUST update the entry to reflect any new field values given in the response.