Amos, assuming Facebook does not listen, is there a way around invalid dates?
I have added the '-i' option to the refresh_pattern. I do not have any other refresh_patterns defined. I like to keep things simple if I can.
Thanks, Norbert
>Amos wrote:
>> General: The Expires header's value isn't a valid date.
> That above is probably the killer. As we get closer to HTTP/1.1
> compliance we get more things discarded for non-compliance.
>
> Invalid date maps to "-1" and non-cacheable.
>
>> refresh_pattern (cgi-bin|\?) 0 0% 0
> The pattern should be -i (/cgi-bin/|\?) for best effect.
>
> Any other refresh_patterns in use? Those URL look suspiciously like
> ones which would be caught by trying to handle mime in refresh_pattern.
