joe chip_pop at hotmail.com
Thu Nov 5 09:54:00 UTC 2015

HI Amos after diging and testing wat i found for you is ....

i will try to explain how dose that happen hoop that im clear enough for you
to understand

ok  lets say the way you guys mod the code for the  TCP_REFRESH_MODIFIED wen
the file expierd or squid think its modified it delete it right or force
newer copy so wat happen here squid thing its swap fail sending wrong flag   

so dont dig as you say for wrong idea   its just in the log or what ever 
its just wrong flag that happen wen it suppose to be  TCP_REFRESH_MODIFIED

that after i spend 24 hr digging  to re produce that error

and pls  put back as it was before   the USE_HTTP_VIOLATIONS and allow us to
decide if that object we need to have it stay longer in cache  

    const char *pattern;
    regex_t compiled_pattern;
    time_t min;
    double pct;
    time_t max;
    RefreshPattern *next;

    struct {
        bool icase;
        bool refresh_ims;
        bool store_stale;
        bool override_expire;
        bool override_lastmod;
        bool reload_into_ims;
        bool ignore_reload;
        bool ignore_no_store;
        bool ignore_must_revalidate;
        bool ignore_private;
        bool ignore_auth;
#endif       missing code that you took of V.4.02   and re mod
TCP_REFRESH_MODIFIED  to have control making the object stay as before that
will correct the issu

View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/TCP-REFRESH-MODIFIED-tp4674325p4674392.html
Sent from the Squid - Users mailing list archive at Nabble.com.

More information about the squid-users mailing list