Bugs item #3487636, was opened at 2012-02-14 10:30
Message generated for change (Comment added) made by bagder
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100976&aid=3487636&group_id=976

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: http
Group: wrong content
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: legalize (legalize)
Assigned to: Daniel Stenberg (bagder)
Summary: Host header omits port number

Initial Comment:
The tracker won't let me comment or reopen bug 3487618, so unfortunately I have to open a new one.

I think you misunderstood the bug report. The problem isn't that the DEFAULT port of 80 isn't included on the header.

The problem is that NON-DEFAULT ports are not included on the header. If you read the RFC, yes, if it is port 80 you can omit the port number on the header. However, if the port number is NOT 80, then you have to include the port number on the header.

You wrote:

"It is also the result of testing as lots of sites actually
break when the default port numbers are provided, or at least they did
years ago when curl did it unconditionally."

I am not saying the default port number should be included in the header, which is why I think you read my bug report backwards.

Thanks.

----------------------------------------------------------------------

>Comment By: Daniel Stenberg (bagder)
Date: 2012-02-14 10:38

Message:
Can you provide an example command line and curl version that repeats this
bug please?

----------------------------------------------------------------------

You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100976&aid=3487636&group_id=976
Received on 2012-02-14