mirror of
https://github.com/moparisthebest/curl
synced 2025-02-28 09:21:50 -05:00
parent
656441d915
commit
ed74c6442d
19
docs/TODO
19
docs/TODO
@ -71,7 +71,7 @@
|
||||
5.9 Improve formpost API
|
||||
5.10 Leave secure cookies alone
|
||||
5.11 Chunked transfer multipart formpost
|
||||
|
||||
5.12 OPTIONS *
|
||||
|
||||
6. TELNET
|
||||
6.1 ditch stdin
|
||||
@ -594,6 +594,23 @@ This is not detailed in any FTP specification.
|
||||
|
||||
https://github.com/curl/curl/issues/1139
|
||||
|
||||
5.12 OPTIONS *
|
||||
|
||||
HTTP defines an OPTIONS method that can be sent with an asterisk option like
|
||||
"OPTIONS *" to ask about options from the server and not a specific URL
|
||||
resource. https://tools.ietf.org/html/rfc7230#section-5.3.4
|
||||
|
||||
libcurl as it currently works will always sent HTTP methods with a path that
|
||||
starts with a slash so there's no way for an application to send a proper
|
||||
"OPTIONS *" using libcurl. This should be fixed.
|
||||
|
||||
I can't think of any other non-slash paths we should support so it will
|
||||
probably make sense to add a new boolean option for issuign an "OPTIONS *"
|
||||
request. CURLOPT_OPTIONSASTERISK perhaps (and a corresponding command line
|
||||
option)?
|
||||
|
||||
See https://github.com/curl/curl/issues/1280
|
||||
|
||||
|
||||
6. TELNET
|
||||
|
||||
|
Loading…
x
Reference in New Issue
Block a user