None of these
$r->err_headers_out->set('Etag' => "-1");
$r->err_headers_out->set('etag' => "-1");
$r->err_headers_out->set('no-etag' => "1");
$r->notes->set('no-etag' => 1);
actually works. Phase where this module runs is PerlHeaderParserHandler, which
is needed
for its DIRECTORY scope. PerlPostReadRequestHandler should be the another
alternative (*)
but it cannot be done in "FILE" scopes.
However the problem is not how to nullify the ETAG value, since it is quite
useful. The
problem is that the server is indeed not serving the real data.
The browser does its job, this is it sends an ETAG value to see if there is any
change in
the content it demands. Then the server should send another etag value, but it
doesn't. It
sends the same value as if it was not seeing that it has new content to serve.
So perhaps the problem is not a headers issue but something different that
causes apache
and/or modperl to not to serve the new pages.
Any idea?? Thanks!
(*)
http://perl.apache.org/docs/2.0/user/handlers/http.html#PerlHeaderParserHandler
>> Additionally, although changing the ETAG is not a good idea (which value i
>> put?), i tried
>> it. The ->unset method is not working, and the ->set method is indeed acting
>> as the ->add
>> method (for example $r->err_headers_out->set('Etag' => "-1");).
>>
>> In all cases, the etag value is again sended.
>try adding this
> $r->notes->set('no-etag' => 1);
>if it doesn't work from your content handler you might need to move this to
>a fixup handler to make sure it's set before apache sends the 304.
>--Geoff
---------------------------------------------------------
Juega y llévate una PS2 two:
http://juegos.ya.com/consolas_y_pc/2005/09/concurso-ps2.html
Ya.com ADSL Navega y habla 24h
ADSL Alta Velocidad + Llamadas Nacionales y Locales + Router Wi-Fi + Cuota
Alta. Todo por 29,95/mes+IVA.
http://acceso.ya.com/ADSLllamadas/4mb
