| Summary: | port no detected when file name not in URL | ||
|---|---|---|---|
| Product: | Apache httpd-2 | Reporter: | Robert Bruce <rob> |
| Component: | mod_vhost_alias | Assignee: | Apache HTTPD Bugs Mailing List <bugs> |
| Status: | RESOLVED LATER | ||
| Severity: | normal | CC: | mengel |
| Priority: | P2 | Keywords: | MassUpdate |
| Version: | 2.2.2 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| URL: | http://apachebug.tdd.org.uk:81 | ||
|
Description
Robert Bruce
2006-06-28 23:18:46 UTC
(In reply to comment #0) We are seeing the same problem, in particular when we should be looking for a DirectoryIndex, it looks in the port 80 server's VirtualDocumentRoot, rather than in the port-numbered server we are coming from. Okay, so after much confusion, I have a workaround for this.
First, you have to use Rewrite based mass virtual hosting, and
second you have to set an environmnent variable (i.e. MY_PORT).
So instead of:
VirtualDocumentRoot /appora/products/web/%0:%p/html
VirtualScriptAlias /appora/products/web/%0:%p/cgi-bin
You need:
RewriteCond %{ENV:MY_PORT} ^$
RewriteRule (.*) $1 [env=MY_PORT:%{SERVER_PORT}]
RewriteMap lowercase int:tolower
RewriteCond %{REQUEST_URI} !/cgi-bin/
RewriteRule ^/(.*)$ /appora/products/web/%{SERVER_NAME}:%{ENV:MY_PORT}/html/$1
RewriteCond %{REQUEST_URI} /cgi-bin/
RewriteRule ^/(.*)$ /appora/products/web/%{SERVER_NAME}:%{ENV:MY_PORT}/$1 [T=application/x-httpd-cgi]
This is the cook book Rewrite based mass virtual hosting, except for the part about setting MY_PORT if it isn't set, and using MY_PORT instead of SERVER_PORT.
Basically, somewhere the SERVER_PORT stuff gets lost when doing things like doing an index.html lookup, but the MY_PORT environment variable doesnt.
Please help us to refine our list of open and current defects; this is a mass update of old and inactive Bugzilla reports which reflect user error, already resolved defects, and still-existing defects in httpd. As repeatedly announced, the Apache HTTP Server Project has discontinued all development and patch review of the 2.2.x series of releases. The final release 2.2.34 was published in July 2017, and no further evaluation of bug reports or security risks will be considered or published for 2.2.x releases. All reports older than 2.4.x have been updated to status RESOLVED/LATER; no further action is expected unless the report still applies to a current version of httpd. If your report represented a question or confusion about how to use an httpd feature, an unexpected server behavior, problems building or installing httpd, or working with an external component (a third party module, browser etc.) we ask you to start by bringing your question to the User Support and Discussion mailing list, see [https://httpd.apache.org/lists.html#http-users] for details. Include a link to this Bugzilla report for completeness with your question. If your report was clearly a defect in httpd or a feature request, we ask that you retest using a modern httpd release (2.4.33 or later) released in the past year. If it can be reproduced, please reopen this bug and change the Version field above to the httpd version you have reconfirmed with. Your help in identifying defects or enhancements still applicable to the current httpd server software release is greatly appreciated. |