Bug#714341: apache2: Disabled Sites Still Served
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 -- To UNSUBSCRIBE, email to debian-apache-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1394598.XMcBXGD9Do@k
Bug#714341: apache2: Disabled Sites Still Served
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 s...@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
Bug#714341: apache2: Disabled Sites Still Served
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? -- Package-specific info: List of enabled modules from 'apache2 -M': alias auth_basic authn_file authz_default authz_groupfile authz_host authz_user autoindex cgid deflate dir env mime negotiation reqtimeout setenvif status -- System Information: Debian Release: 7.1 Architecture: armhf (armv6l) Kernel: Linux 3.6.11+ (PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages apache2 depends on: ii apache2-mpm-worker 2.2.22-13 ii apache2.2-common2.2.22-13 apache2 recommends no packages. apache2 suggests no packages. Versions of packages apache2.2-common depends on: ii apache2-utils 2.2.22-13 ii apache2.2-bin 2.2.22-13 ii lsb-base 4.1+Debian8+rpi1 ii mime-support 3.52-1 ii perl 5.14.2-21+rpi1 ii procps 1:3.3.3-3 Versions of packages apache2.2-common recommends: ii ssl-cert 1.0.32 Versions of packages apache2.2-common suggests: pn apache2-doc none pn apache2-suexec | apache2-suexec-custom none ii dillo [www-browser] 3.0.2-2 ii midori [www-browser]0.4.3+dfsg-0.1 ii netsurf-gtk [www-browser] 2.9-2 -- no debconf information -- To UNSUBSCRIBE, email to debian-apache-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130628060147.3585.99821.reportbug@legendspi
