[svn] Removed statement that redirect in response to POST is "technically

disallowed", which I cannot find in rfc2616 nor in rfc1945.  Even if that
were technically the case, the widespreadedness of such responses would make
the prohibition irrelevant.

diff --git a/doc/ChangeLog b/doc/ChangeLog
index be7a6120a525488b089dc65e6c53aa72765fe9f1..651e7db5fc9b54a4f05390e908a0a511f7c2a039 100644 (file)
--- a/doc/ChangeLog
+++ b/doc/ChangeLog
@@ -1,3 +1,11 @@
+2005-05-30  Hrvoje Niksic  <hniksic@xemacs.org>
+
+       * wget.texi (HTTP Options): Removed statement that redirect in
+       response to POST is "technically disallowed", which I cannot find
+       in rfc2616 nor in rfc1945.  Even if that were technically the
+       case, the widespreadedness of such responses would make the
+       prohibition irrelevant.
+
 2005-05-14  Hrvoje Niksic  <hniksic@xemacs.org>
 
        * wget.texi (Overview): Document --[no-]proxy as primarily being

diff --git a/doc/wget.texi b/doc/wget.texi
index 5f72c35a3ce849fd3e166d1bb13df69394808fc3..dfd87e06f492c6be5e9024161da104350c783545 100644 (file)
--- a/doc/wget.texi
+++ b/doc/wget.texi
@@ -1311,12 +1311,12 @@ use chunked unless it knows it's talking to an HTTP/1.1 server.  And it
 can't know that until it receives a response, which in turn requires the
 request to have been completed -- a chicken-and-egg problem.
 
-Note: if Wget is redirected after the POST request is completed, it will
-not send the POST data to the redirected URL.  This is because URLs that
-process POST often respond with a redirection to a regular page
-(although that's technically disallowed), which does not desire or
-accept POST.  It is not yet clear that this behavior is optimal; if it
-doesn't work out, it will be changed.
+Note: if Wget is redirected after the POST request is completed, it
+will not send the POST data to the redirected URL.  This is because
+URLs that process POST often respond with a redirection to a regular
+page, which does not desire or accept POST.  It is not completely
+clear that this behavior is optimal; if it doesn't work out, it might
+be changed in the future.
 
 This example shows how to log to a server using POST and then proceed to
 download the desired pages, presumably only accessible to authorized