Bug 65078 - Protocol directive vs. Listen directive defaults
Summary: Protocol directive vs. Listen directive defaults
Status: RESOLVED FIXED
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: Documentation (show other bugs)
Version: 2.5-HEAD
Hardware: All All
: P2 minor (vote)
Target Milestone: ---
Assignee: HTTP Server Documentation List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-01-14 01:49 UTC by Christoph Anton Mitterer
Modified: 2021-01-14 03:19 UTC (History)
0 users


Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Christoph Anton Mitterer 2021-01-14 01:49:16 UTC 
Hey.

In mod/core.html Listen says it defaults to https for 443 and http for everything else.

However, the protocol directive claims http would only be assumed for port 80.

AFAICS from the sources, these are identical wrt the protocol, so shouldn't it also default to https for all but 443?

If so, please adapt the docs :-)

Cheers,
Chris.
Comment 1 Eric Covener 2021-01-14 02:49:38 UTC 
> AFAICS from the sources, these are identical wrt the protocol, so shouldn't
> it also default to https for all but 443?

Do you mean "http" here?
Comment 2 Eric Covener 2021-01-14 03:02:24 UTC 
I've copied the Listen paragraph to Protocol replacing the beginning with "this directive..."
Comment 3 Christoph Anton Mitterer 2021-01-14 03:19:53 UTC 
> Do you mean "http" here?

Yes, sorry for the confusion.


Perhaps the "Protocol" directive should be removed altogether... not only is it confusing with the "Protocols" directive... it also intersects with "Listen"... and opens questions like:
- to which addr:ports does it actually apply (e.g. if there are several in the <VirtualHost>... and maybe some of them even in multple vhosts with different "Protocol" set.
- which one wins if both, "Listen" and "Protocol" is set


Thanks for the update to the docs, though :-)

Chris.