moparisthebest/curl - curl - code.moparisthebest.com

Commit Graph

Author	SHA1	Message	Date
Dan Fandrich	348f8a3da9	test1260: added http as a required feature	2017-03-08 09:06:56 +01:00
Dan Fandrich	3914c07ed6	test1260: removed errant XML tag	2017-03-06 23:05:51 +01:00
Daniel Stenberg	aadb7c7b62	URL: return error on malformed URLs with junk after port number ... because it causes confusion with users. Example URLs: "http://[127.0.0.1]:11211:80" which a lot of languages' URL parsers will parse and claim uses port number 80, while libcurl would use port number 11211. "http://user@example.com:80@localhost" which by the WHATWG URL spec will be treated to contain user name 'user@example.com' but according to RFC3986 is user name 'user' for the host 'example.com' and then port 80 is followed by "@localhost" Both these formats are now rejected, and verified so in test 1260. Reported-by: Orange Tsai	2017-03-06 16:08:21 +01:00

Author

SHA1

Message

Date

Dan Fandrich

348f8a3da9

test1260: added http as a required feature

2017-03-08 09:06:56 +01:00

Dan Fandrich

3914c07ed6

test1260: removed errant XML tag

2017-03-06 23:05:51 +01:00

Daniel Stenberg

aadb7c7b62

URL: return error on malformed URLs with junk after port number

... because it causes confusion with users. Example URLs:

"http://[127.0.0.1]:11211:80" which a lot of languages' URL parsers will
parse and claim uses port number 80, while libcurl would use port number
11211.

"http://user@example.com:80@localhost" which by the WHATWG URL spec will
be treated to contain user name 'user@example.com' but according to
RFC3986 is user name 'user' for the host 'example.com' and then port 80
is followed by "@localhost"

Both these formats are now rejected, and verified so in test 1260.

Reported-by: Orange Tsai

2017-03-06 16:08:21 +01:00

3 Commits