Scenario is as follows:
1. You post a form (.e.g. to Swiki, etc.).
2. The form is successfully processed.
3) The result you get is a redirection to another page which has a
different authentication (or you prefer to reauthenticate instead of
keeping the pass around). 
The problem becomes as follows:
1) At this point HTTPSocket does the redirection internally.
2) HTTPSocket now returns the content after redirection. This content is
"Authorization Failed".
3) Now, HttpUrl object gets this content and applies
checkAuthentication:retry: to it.
4) As there is a failure, HttpUrl reposts the orginal form. 
5) If the post action does not fail for another reason this reposting
goes on infinitely.

For example, you can try to create a new swiki book using scamper.
Fortunately you, as swiki does not allow you to create the same book
twice, you will break out of this loop with a failure: "This name
already exists". 

I could not come up with an easy solution as it is involving more than
one heavily used class.

Note: In order to attempt form posting sensibly, you need to first
fileIn the changeSet included in topic "[FIX] Scamper-Form Submit-umur
([sm][cd][et])"

Umur