Re: [us...@httpd] virtualhost not picking up for non port 80

ok i found what was wrong, so i checked out my code from SVN into htdocs folder out of convenience. that was why the directory allow from all was failing and it was using the main servername instead. so the moral of this story is, do not use svn on the files/folders of your documentroot i lost 2 d

Re: [us...@httpd] virtualhost not picking up for non port 80

i checked the ports, when apache is down, its clear i changed the virtual host to localhost:8886 and telnet localhost 8886 is successful i turned off my antivirus, although it shouldn't affect localhost On Mon, Apr 12, 2010 at 3:33 PM, Frank Gingras wrote: > Michael, > > Start apache, check net

Re: [us...@httpd] virtualhost not picking up for non port 80

Michael, Start apache, check netstat -plant for the process, then try to telnet to the port on localhost. If that fails, it's probably a firewall issue. Frank. On 04/12/2010 06:01 PM, Michael Ni wrote: yes my virtual host tag has 192.168.0.10:8886 and the listen di

Re: [us...@httpd] virtualhost not picking up for non port 80

yes my virtual host tag has 192.168.0.10:8886 and the listen directive was Listen 8886 i have NameVirtualHost 192.168.0.10:80 as well for some reason its not detecting, there is some logic somewhere saying, if port is not 80 and main configuration is listening for port, redirect to that port, if

Re: [us...@httpd] virtualhost not picking up for non port 80

The conf VirtualHost must include the hostname and the port. You could just add * to indicate it should listen to all ports. I'm not sure what teh 8886 port has to do with your problem - not sure it has antyhing to do with it. You need a Listen *:80 or 192.168.1.1:80 for it to listen on port 8

Re: [us...@httpd] virtualhost not picking up for non port 80

tried it, still doesn't work, i dont think it needs to be that specific right? Listen 192.168.0.10 should work. On Mon, Apr 12, 2010 at 8:07 AM, alin vasile wrote: > in httpd.conf it shouldn't be > > Listen 192.168.0.10 :8886? > > -- > *Fro

Re: [us...@httpd] apache2.2 + ssl

mod_redirect if it's something you want to force. On 4/12/10 3:35 PM, motty.cruz wrote: Hello, I have apache 2.2 running on FreeBSD. Apache is working fine but when I go to Machinename.domain.com defaults to http://machine.domain.com/ instead of https://machine.domain.com/ I have look ar

RE: [us...@httpd] apache2.2 + ssl (UNCLASSIFIED)

Classification: UNCLASSIFIED Caveats: NONE Use mod_rewrite, see apache documentation for details (http://httpd.apache.org/docs/2.2/ssl/ssl_faq.html). Here's how to use mod_rewrite to redirect http to https: http://httpd.apache.org/docs/2.2/ssl/ssl_faq.html#relative. Ensure that you have a

[us...@httpd] apache2.2 + ssl

Hello, I have apache 2.2 running on FreeBSD. Apache is working fine but when I go to Machinename.domain.com defaults to http://machine.domain.com/ instead of https://machine.domain.com/ I have look around, I don't see to get a solid answer to get apache to rederect users to https not http An

[us...@httpd] FW: HTTPS Connection Timeouts

Hi, We are using Apache server version 1.3.37 on Unix, and we occasionally get a lot of https connections at the same time (or thereabouts) to some CGI's. Some of these https connections are getting a timeout, and in particular, a connection to a CGI that we use monitor things with to this site fr

Re: [us...@httpd] Headers Spanning in multiple TCP segment.

On Sun, Apr 11, 2010 at 2:45 PM, rangeli nepal wrote: > Just to verify my suspicion about the payload I set the authorization header > to my name. It works well.  I mean it went well fore small pay load. > However, with the token it determines that it is a bad request before it get > the full head

Re: [us...@httpd] virtualhost not picking up for non port 80

in httpd.conf it shouldn't be Listen 192.168.0.10:8886? From: Michael Ni To: users@httpd.apache.org Sent: Mon, April 12, 2010 5:39:42 PM Subject: Re: [us...@httpd] virtualhost not picking up for non port 80 yes i have Listen 8886 in the httpd.conf file i

Re: [us...@httpd] virtualhost not picking up for non port 80

yes i have Listen 8886 in the httpd.conf file i tried changing the private ip to localhost, it doesn't work as well On Mon, Apr 12, 2010 at 7:33 AM, Frank Gingras wrote: > Michael, > > Make sure you have a corresponding Listen directive before your vhost as > well for that port. > > Frank. >

Re: [us...@httpd] virtualhost not picking up for non port 80

Michael, Make sure you have a corresponding Listen directive before your vhost as well for that port. Frank. On 04/12/2010 10:20 AM, Michael Ni wrote: i added log in virtual host ErrorLog "logs/asdf-error.log" CustomLog "logs/asdf-access.log" common when i tried again, nothing shows

Re: [us...@httpd] virtualhost not picking up for non port 80

i added log in virtual host ErrorLog "logs/asdf-error.log" CustomLog "logs/asdf-access.log" common when i tried again, nothing shows up on both i also did a httpd -S and got the following C:\Program Files\Apache Software Foundation\Apache2.2\bin>httpd -S VirtualHost configuration: 192.168.

Re: [us...@httpd] virtualhost not picking up for non port 80

Am 12.04.2010 16:00, schrieb Michael Ni: I'm having difficulty on windows XP getting a virtualhost to work with non port 80. it works when i use port 80 in the virtualhost but doesn't work with other ports. i have turned off my firewall, although this is private ip, shouldn't matter i have tri

[us...@httpd] virtualhost not picking up for non port 80

I'm having difficulty on windows XP getting a virtualhost to work with non port 80. it works when i use port 80 in the virtualhost but doesn't work with other ports. i have turned off my firewall, although this is private ip, shouldn't matter i have tried ports 8080, , 8000, and now with 8886.

Re: [us...@httpd] Centralized logging.

On Thu, 2010-04-08 at 13:52 -0700, Ray Van Dolson wrote: > So how are people out there in mailing list land handling centralized > logging? > > I'd like to mirror my web farm's logfiles on a central server, but want > to be sure to preserve the W3C-ness so it's easy to run awstats, etc > against t