-
Notifications
You must be signed in to change notification settings - Fork 89
/
_resources.html
82 lines (71 loc) · 3 KB
/
_resources.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
#include "_doctype.html"
<HTML>
<HEAD> <TITLE>curl - Resources</TITLE>
#include "css.t"
</HEAD>
#define CURL_RESOURCES
#include "_menu.html"
#include "setup.t"
TITLE(Resources)
<p>
This document has been introduced in order to let you find documents that
specify standards used by curl, software that extends curl, and web pages with
"competing" utilities.
TITLE(Standards)
<p>
<pre>
RFC 959 - Defines how FTP works
RFC 1738 - Uniform Resource Locators
RFC 1777 - defines the LDAP protocol
RFC 1808 - Relative Uniform Resource Locators
RFC 1867 - Form-based File Upload in HTML
RFC 1950 - ZLIB Compressed Data Format Specification
RFC 1951 - DEFLATE Compressed Data Format Specification
RFC 1952 - gzip compression format
RFC 1959 - LDAP URL syntax
RFC 2045-2049 - Everything you need to know about MIME! (needed for form
based upload)
RFC 2068 - HTTP 1.1 (obsoleted by RFC 2616)
RFC 2109 - HTTP State Management Mechanism (cookie stuff)
RFC 2183 - "The Content-Disposition Header Field"
RFC 2229 - "A Dictionary Server Protocol"
RFC 2231 - "MIME Parameter Value and Encoded Word Extensions:
Character Sets, Languages, and Continuations"
RFC 2388 - "Returning Values from Forms: multipart/form-data"
Use this as an addition to the 1867
RFC 2396 - "Uniform Resource Identifiers: Generic Syntax and Semantics"
This one obsoletes 1738, but since 1738 is often mentioned I've left it
in this list.
RFC 2428 - "FTP Extensions for IPv6 and NATs"
This should be considered when introducing IPv6 awareness.
RFC 2616 - HTTP 1.1
RFC 2617 - HTTP Authentication
HTTP/1.1 rev 6 (internet draft) - This defines some interesting new things
that differs from the RFC2068 definitions. CONNECT being one of the most
obvious.
https://www.w3.org/Protocols/HTTP/1.1/draft-ietf-http-v11-spec-rev-06.txt
"Tunneling TCP based protocols through Web proxy servers" - This is what
describes how to use SSL connections through a web proxy.
https://www.ietf.org/internet-drafts/draft-luotonen-web-proxy-tunneling-01.txt
</pre>
TITLE(Compilers)
<pre>
MingW32 - <a href="http://www.xraylith.wisc.edu/~khan/software/gnu-win32/index.html">http://www.xraylith.wisc.edu/~khan/software/gnu-win32/index.html</a>
</pre>
TITLE(Software)
<pre>
OpenSSL - <a href="https://www.openssl.org">https://www.openssl.org</a>
OpenLDAP - <a href="https://www.openldap.org">https://www.openldap.org</a>
zlib - <a href="http://www.cdrom.com/pub/infozip/zlib/">http://www.cdrom.com/pub/infozip/zlib/</a>
</pre>
TITLE(Competitors)
<pre>
wget - <a href="https://www.gnu.org/software/wget/">https://www.gnu.org/software/wget/</a>
snarf - <a href="https://www.xach.com/snarf/">https://www.xach.com/snarf/</a>
lynx - <a href="http://lynx.browser.org/">http://lynx.browser.org/</a> (well at least when -dump is used)
swebget - <a href="https://www.uni-hildesheim.de/~smol0075/swebget/">https://www.uni-hildesheim.de/~smol0075/swebget/</a>
fetch - ?
</pre>
#include "_footer.html"
</BODY>
</HTML>