gnunet-svn
[Top][All Lists]
Advanced

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

[GNUnet-SVN] [gnurl] 167/173: TODO: "OPTIONS *"


From: gnunet
Subject: [GNUnet-SVN] [gnurl] 167/173: TODO: "OPTIONS *"
Date: Fri, 24 Feb 2017 14:03:09 +0100

This is an automated email from the git hooks/post-receive script.

ng0 pushed a commit to annotated tag gnurl-7.53.1
in repository gnurl.

commit ed74c6442d8f46cae448e8b90130d006eb6169f5
Author: Daniel Stenberg <address@hidden>
AuthorDate: Thu Feb 23 16:58:21 2017 +0100

    TODO: "OPTIONS *"
    
    Closes #1280
---
 docs/TODO | 19 ++++++++++++++++++-
 1 file changed, 18 insertions(+), 1 deletion(-)

diff --git a/docs/TODO b/docs/TODO
index 217c6f887..15c1b274f 100644
--- a/docs/TODO
+++ b/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
 

-- 
To stop receiving notification emails like this one, please contact
address@hidden



reply via email to

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