Marco Stoecker wrote:
> If I've read the thread carefully and I thought that I indeed have a similar
> problem as Daniel has, which in summary means "If you disable the default
> site via a2dissite, it will nevertheless show the index.html in
> /var/www/html, when you call localhost or the dedicate
On 05/08/2015 09:54 PM, Bob Proulx wrote:
Marco Stoecker wrote:
Bob Proulx wrote:
> I am unable to recreate your problem on wheezy. I just now installed
>...
> Go back and double check everything.
But what happens to the mailman site, if I disable listening on port
80?
Will the mailman site
On 04/05/15 05:21, Georgi Naplatanov wrote:
>> Currently I have a unique site in sites-enabled which is accessed only
>> via HTTPS. Hoping to have an access error when trying to access this
>> site via HTTP, Apache sends me to the default site which is "It's
>> works!" page in /var/www/html.
>>
>>
Hi, Bob.
On 08/05/15 16:54, Bob Proulx wrote:
> Daniel Bareiro submitted the problem that he could not disable the
> default web server on port 80. That has been the topic of this
> thread.
>
> I see now that you did say you wanted to have the mailman site
> enabled. I didn't see that before s
On 09/05/15 10:19, Daniel Bareiro wrote:
> I would prefer using _default_ because that way it will return 404 when
> there is not a match for the site name.
A curious question about this: Is there any way that Apache responds
similarly to the way it does Nginx with its error code 444 (the server
Hi, Marco.
On 07/05/15 04:29, Marco Stoecker wrote:
> But what happens to the mailman site, if I disable listening on port 80?
> Will the mailman site still be available?
This suggests that you have Mailman listening on port 80 not https. So
here I think the alternative to avoid behavior "catch-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/05/15 14:22, Marco Stoecker wrote:
> Hi Bob
Hi, Bob and Marco.
Bob, I appreciate your interest and time spent in testing.
> thanks for your help. I did it the other way. Just installed wheezy
> on a 2nd machine, installed apache2, disabled th
Marco Stoecker wrote:
> Bob Proulx wrote:
> > I am unable to recreate your problem on wheezy. I just now installed
> >...
> > Go back and double check everything.
>
> But what happens to the mailman site, if I disable listening on port 80?
> Will the mailman site still be available?
(Me rattles
On 05/07/2015 08:31 AM, Bob Proulx wrote:
Marco Stoecker wrote:
thanks for your help. I did it the other way. Just installed wheezy on
a 2nd machine, installed apache2, disabled the default site and still,
if I call http://192.168.10.16, it shows the default site.
I am unable to recreate your
Marco Stoecker wrote:
> thanks for your help. I did it the other way. Just installed wheezy on
> a 2nd machine, installed apache2, disabled the default site and still,
> if I call http://192.168.10.16, it shows the default site.
I am unable to recreate your problem on wheezy. I just now installed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/06/2015 01:09 AM, Bob Proulx wrote:
> Daniel Bareiro wrote:
>> Marco Stoecker wrote:
>>> I do have the same issue. I disabled the default config in
>>> "sites-enabled" (which in fact removed the symbolic link to
>>> the 000-default.conf in "site
On 05/04/2015 12:10 PM, Daniel Bareiro wrote:
> Thanks for confirm the behavior that I had mentioned. I don't remember
> this happening with Apache 2.2.22 on Debian Wheezy. So at the beginning
> of this thread I had asked whether it is likely that this configuration
> is compiled into Apache.
>
>
Daniel Bareiro wrote:
> Marco Stoecker wrote:
> > I do have the same issue. I disabled the default config in
> > "sites-enabled" (which in fact removed the symbolic link to the
> > 000-default.conf in "sites-available") and did a restart of apache, but
> > still the default page is showing up. I th
On 04/05/15 04:50, Marco Stoecker wrote:
> Hi Bob,
Hi, Marco.
> I do have the same issue. I disabled the default config in
> "sites-enabled" (which in fact removed the symbolic link to the
> 000-default.conf in "sites-available") and did a restart of apache, but
> still the default page is showi
On 04/30/2015 10:23 PM, Daniel Bareiro wrote:
> Hi all!
>
> Currently I have a unique site in sites-enabled which is accessed only
> via HTTPS. Hoping to have an access error when trying to access this
> site via HTTP, Apache sends me to the default site which is "It's
> works!" page in /var/www/h
Hi Bob,
I do have the same issue. I disabled the default config in
"sites-enabled" (which in fact removed the symbolic link to the
000-default.conf in "sites-available") and did a restart of apache, but
still the default page is showing up. I there another way to disable the
default site? I'd
Daniel Bareiro wrote:
> Case 2:
> [I disabled the 000-default]
>...
> Case 3:
> [Now I disable additionally default.freesoftware.conf]
>...
> Despite not being enabled 000-default, would be expected this behavior?
Did you restart the server after making your config file changes? You
didn't mentio
On 02/05/15 14:57, Daniel Bareiro wrote:
> I will continue investigating.
Well, I was doing some testing:
(Server listening on ports 80 and 443)
Case 1:
---
root@mail:/etc/apache2/sites-enabled# ll
total 0
lrwxrwxrwx 1 root root 35 may 2 19:02 000-default.conf ->
../sites-available/000-def
Hi, Bob.
On 01/05/15 17:30, Bob Proulx wrote:
>> Currently I have a unique site in sites-enabled which is accessed only
>> via HTTPS. Hoping to have an access error when trying to access this
>> site via HTTP, Apache sends me to the default site which is "It's
>> works!" page in /var/www/html.
>>
On 2015-04-30, Daniel Bareiro wrote:
> Hi all!
>
> Currently I have a unique site in sites-enabled which is accessed only
> via HTTPS. Hoping to have an access error when trying to access this
> site via HTTP, Apache sends me to the default site which is "It's
> works!" page in /var/www/html.
>
>
Daniel Bareiro wrote:
> Currently I have a unique site in sites-enabled which is accessed only
> via HTTPS. Hoping to have an access error when trying to access this
> site via HTTP, Apache sends me to the default site which is "It's
> works!" page in /var/www/html.
>
> I was looking in the Apache
Hi, Dan.
On 30/04/15 16:34, Dan Ritter wrote:
>> Currently I have a unique site in sites-enabled which is accessed only
>> via HTTPS. Hoping to have an access error when trying to access this
>> site via HTTP, Apache sends me to the default site which is "It's
>> works!" page in /var/www/html.
>>
On Thu, Apr 30, 2015 at 04:23:20PM -0300, Daniel Bareiro wrote:
> Hi all!
>
> Currently I have a unique site in sites-enabled which is accessed only
> via HTTPS. Hoping to have an access error when trying to access this
> site via HTTP, Apache sends me to the default site which is "It's
> works!"
Hi all!
Currently I have a unique site in sites-enabled which is accessed only
via HTTPS. Hoping to have an access error when trying to access this
site via HTTP, Apache sends me to the default site which is "It's
works!" page in /var/www/html.
I was looking in the Apache configuration files wher
24 matches
Mail list logo
