Page History

...

Whom do I contact for support?

See httphttps://httpd.apache.org/support.html.

...

The occasional availability of binaries for one platform or another at httphttps://httpd.apache.org/dist/httpd/binaries/ has been a source of confusion for the user community, particularly the large subset which uses the Windows platform and is not able to build httpd and prerequisites themselves.

...

The detailed answer to this question can be found in the Apache license, which is included in the Apache distribution in the file LICENSE. You can also find it on the Web at httphttps://www.apache.org/licenses/.

...

You need to use it with a URL in the form "/foo/bar" and not one with a method and hostname such as "httphttps://host/foo/bar". See the ErrorDocument documentation for details. This was incorrectly documented in the past.

...

You may want to check out the Apache Week article entitled: "Gathering Visitor Information: Customizing Your Logfiles".

Why does accessing directories only work when I include the trailing "/" (e.g.,

...

https://foo.domain.com/~user/) but not when I omit it (e.g.,

...

https://foo.domain.com/~user)?

When you access a directory without a trailing "/", Apache needs to send what is called a redirect to the client to tell it to add the trailing slash. If it did not do so, relative URLs would not work properly. When it sends the redirect, it needs to know the name of the server so that it can include it in the redirect. There are two ways for Apache to find this out; either it can guess, or you can tell it. If your DNS is configured correctly, it can normally guess without any problems. If it is not, however, then you need to tell it.

...

The above directive creates an alias for URLs starting with /example/, but does not alias URLs starting with /example. That is to say, a URL such as httphttps://servername.com/example/ will get the desired content, but a URL such as httphttps://servername.com/example will result in a "file not found" error.

...

Use mod_rewrite as described in the "Canonical Hostnames" section of the URL Rewriting Guide.

See httphttps://httpd.apache.org/docs/current/rewrite/remapping.html#canonicalhost .

...

There are many possible reasons for this, and almost all of them are related to the configuration of your network, not the configuration of the Apache HTTP Server. One of the most common problems is that a firewall blocks access to the default HTTP port 80. In particular, many consumer ISPs block access to this port. You can see if this is the case by changing any Port and Listen directives in httpd.conf to use port 8000 and then request your site using httphttps://yourhost.example.com:8000/. (Of course, a very restrictive firewall may block this port as well.)

...

There is a collection of practical solutions that can be found in the URL Rewriting Guide. If you have more interesting rulesets which solve particular problems not currently covered in this document, open a doc suggestion in bugzilla to add it. The other webmasters will thank you for avoiding the reinvention of the wheel.

Where can I find any published information about URL-manipulations and mod_rewrite?

There is an article from Ralf S. Engelschall about URL-manipulations based on mod_rewrite in the "iX Multiuser Multitasking Magazin" issue #12/96. The German (original) version can be read online at <http://www.heise.de/ix/artikel/1996/12/149/>, the English (translated) version can be found at <http://www.heise.de/ix/artikel/E/1996/12/149/>.

Why is mod_rewrite so difficult to learn and seems so complicated?

...