From 658b9a200ae2b31dfe7ede957fb5aaa127386205 Mon Sep 17 00:00:00 2001 From: Sylvestre Ledru Date: Sat, 4 Mar 2017 15:50:33 +0100 Subject: fix some typos in the doc (#1306) --- docs/libcurl/libcurl-tutorial.3 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'docs/libcurl') diff --git a/docs/libcurl/libcurl-tutorial.3 b/docs/libcurl/libcurl-tutorial.3 index 3144da3c6..cbfb081dc 100644 --- a/docs/libcurl/libcurl-tutorial.3 +++ b/docs/libcurl/libcurl-tutorial.3 @@ -1147,7 +1147,7 @@ behind a firewall. Apps can mitigate against this by using the .IP "IPv6 Addresses" libcurl will normally handle IPv6 addresses transparently and just as easily as IPv4 addresses. That means that a sanitizing function that filters out -addressses like 127.0.0.1 isn't sufficient--the equivalent IPv6 addresses ::1, +addresses like 127.0.0.1 isn't sufficient--the equivalent IPv6 addresses ::1, ::, 0:00::0:1, ::127.0.0.1 and ::ffff:7f00:1 supplied somehow by an attacker would all bypass a naive filter and could allow access to undesired local resources. IPv6 also has special address blocks like link-local and site-local -- cgit v1.2.3