Bug#714341: apache2: Disabled Sites Still Served

[ash martin <ashmrtn17@gmail.com>]

Unfortunately the problem still persists when apache is reloaded. The virtual host is also still served when I use a command line tool like curl so it is not a caching issue either.

On Sun, Jul 14, 2013 at 2:47 PM, Stefan Fritsch <sf@sfritsch.de> wrote:

Am Freitag, 28. Juni 2013, 00:01:47 schrieb lastlegends:

> Package: apache2.2-common
> Version: 2.2.22-13
> Severity: important
>
> Hello,
>       I am running apache on the raspian wheezy version of a raspberry
pi
> (because I can). However, whenever I use a2dissite to disable a
> site and then navigate to the site in any browser I find that the
> site is still served. This problem also persisted in a VM install
> of debian 7.1 and was also present in the 2.4 release of Apache2.
> Am I just missing something really obvious or this an actual issue?

Two ideas:

- Did you maybe forget to reload the apache2 configuration as prompted
by a2dissite?
- Maybe the browser or some proxy on the way still has the pages
cached. Depending on the browser, it may be difficult to actually
force it to reload the page from the server. Trying with a commandline
client is usually more reliable for testing. Try e.g. curl