[privoxy-users] [ ijbswa-Support Requests-3532010 ] Make Privoxy retry on 503 ?

[SourceForge.net <no...@so...>]

Support Requests item #3532010, was opened at 2012-06-04 15:47
Message generated for change (Settings changed) made by rantrinmonk
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=211118&aid=3532010&group_id=11118

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: actions files
Group: None
>Status: Closed
Priority: 5
Private: No
Submitted By: Romico (rantrinmonk)
Assigned to: Fabian Keil (fabiankeil)
Summary: Make Privoxy retry on 503 ?

Initial Comment:
Hi, I'm using Privoxy to redirect a request for a binary file from one server to another. The problem is that the server sometimes will return a 503 status code because it's a cache server. If I retry a few times to get the file the server eventually will respond correctly.
Is there any way to make Privoxy retry the request when the server respond with a 503 status?

----------------------------------------------------------------------

Comment By: Romico (rantrinmonk)
Date: 2012-06-06 18:41

Message:
Thanks, I'll try that.

----------------------------------------------------------------------

Comment By: Fabian Keil (fabiankeil)
Date: 2012-06-06 09:01

Message:
You can't let Privoxy itself retry on getting a 503, but you can let the
client retry.

To do that:

1. Use a server-header-tagger to tag such responses.
2. Use the resulting tag to enable a +redirect{} action that redirects
    the client to another URL that contains the original URL.
3. Catch the resulting client request with
+fast-redirects{check-decoded-url}
    to redirect it to the original URL again.

Note that this circumvents Privoxy's redirect loop detection, so if the
client doesn't check for redirect loops either and the server doesn't
stop sending 503 responses, you'll get a redirect loop.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=211118&aid=3532010&group_id=11118