www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adam Pedersen" <a...@adeptsoftware.com>
Subject Re: general/9771: alias fails
Date Sun, 10 Feb 2002 21:07:06 GMT
ServerName is NOT misconfigured.  VHosts are also matched on ServerAlias - why does ServerAlias
even exist if references without a trailing "/" are going to fail.

Marc is right - this is not related to alias.  But this is a BUG.  Why does it take a jackhammer
for you to consider that possibility?  Open Source duplicates the beauracracy of big corporations
very well.

----- Original Message ----- 
  From: rbb@apache.org 
  To: adam@adeptsoftware.com ; apache-bugdb@apache.org ; rbb@apache.org 
  Sent: Saturday, February 09, 2002 4:49 PM
  Subject: Re: general/9771: alias fails

  [In order for any reply to be added to the PR database, you need]
  [to include <apbugs@Apache.Org> in the Cc line and make sure the]
  [subject line starts with the report component and number, with ]
  [or without any 'Re:' prefixes (such as "general/1098:" or      ]
  ["Re: general/1098:").  If the subject doesn't match this       ]
  [pattern, your message will be misfiled and ignored.  The       ]
  ["apbugs" address is not added to the Cc line of messages from  ]
  [the database automatically because of the potential for mail   ]
  [loops.  If you do not include this Cc, your reply may be ig-   ]
  [nored unless you are responding to an explicit request from a  ]
  [developer.  Reply only with text; DO NOT SEND ATTACHMENTS!     ]

  Synopsis: alias fails

  Comment-Added-By: rbb
  Comment-Added-When: Sat Feb  9 14:49:19 PST 2002
  You are not paying attention to what Marc said.  The /icons/ request will succeed regardless
of the ServerName's configuration, but /icons will only succeed if ServerName is setup properly.

  The reason is simple once you understand it.  If the server gets a request for /icons it
must return a response to the client that says that the resource has been moved permanently.
 This means that the server will respond to your client telling it to request /icons/.  However,
if your ServerName is misconfigured, then the server will put the wrong servername in the
response, and the redirect will fail.

  For /icons/ the server handles everything internally, which means that the ServerName configuration
doesn't matter, the server uses the ServerName attached to the original request.

  The reason we don't automatically use the ServerName attached to the original request for
the redirect case, is that it may not work properly.  Think of the case where the server is
behind a proxy, so you want to return the name of the proxy instead of the name of the origin
server to the client.

  I hope that explains the problem more clearly.  This is a mis-configuration of the server,
and if you fix the ServerName directive, your problem should go away.

View raw message