wget-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Wget-dev] wget2 | Unimplemented options '--body-data' and '--body-file'


From: Rohan Fletcher
Subject: [Wget-dev] wget2 | Unimplemented options '--body-data' and '--body-file' (#437)
Date: Mon, 29 Apr 2019 14:27:05 +0000


New Issue was created.

Issue 437: https://gitlab.com/gnuwget/wget2/issues/437
Author:    Rohan Fletcher
Assignee:  

The options `--body-data` and `--body-file` are unimplemented

>From the docs:

> ### `--body-data=Data-String`, `--body-file=Data-File` \[Not implemented yet\]
> 
> Must be set when additional data needs to be sent to the server along with 
> the Method specified using `--method`. `--body-data` sends string as data, 
> whereas --body-file sends the contents of file. Other than that, they work in 
> exactly the same way.
> 
> Currently, `--body-file` is not for transmitting files as a whole. Wget2 does 
> not currently support "multipart/form-data" for transmitting data; only 
> "application/x-www-form-urlencoded". In the future, this may be changed so 
> that wget2 sends the --body-file as a complete file instead of sending its 
> contents to the server. Please be aware that Wget2 needs to know the contents 
> of BODY Data in advance, and hence the argument to --body-file should be a 
> regular file. See --post-file for a more detailed explanation. Only one of 
> --body-data and --body-file should be specified.
> 
> If Wget2 is redirected after the request is completed, Wget2 will suspend the 
> current method and send a GET request till the redirection is completed. This 
> is true for all redirection response codes except 307 Temporary Redirect 
> which is used to explicitly specify that the request method should not 
> change. Another exception is when the method is set to "POST", in which case 
> the redirection rules specified under `--post-data` are followed.

-- 
Reply to this email directly or view it on GitLab: 
https://gitlab.com/gnuwget/wget2/issues/437
You're receiving this email because of your account on gitlab.com.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]