Gary,
In general, the client, normally a web browser, knows that https is done over port 443. So most browsers will go to port
443 automatically when the URL begins with https. There is really no way to 'trick' the browser from the server-side. I
assume that the idea of moving the HTTPS listener
Is there a way to have Apache 2.2 output access logs in W3C "Extended Log Format"? I'm specifically trying to get
elapsed request time into the log, in a standard way, so that I can pick the value up in WebTrends 7. It seems like the
W3C format is the only way that it can get into the log and be
I found the problem. Apparently the directive "Listen 80" doesn't work, so I made it more specific to "Listen
12.34.56.78:80", of course where 12.34.56.78 is my IP address and it worked like a charm.
Bernie
Bernie Durfee wrote:
...which looks okay, but Apache seems
...which looks okay, but Apache seems to crash and never
starts listening. I only get the following in the logs directory...
"...seems to crash..." - that's a bit vague...
Sorry, it does crash or at least doesn't completely start.
- is httpd running (ps -ef)?
- what happens if you try to acc
I have been unable to get Apache 2.2.0 with SSL running on AIX 5.3. This is from
"httpd -V"...
Server version: Apache/2.2.0
Server built: Mar 28 2006 11:28:41
Server's Module Magic Number: 20051115:0
Architecture: 32-bit
Server MPM: Prefork
threaded: no
forked: yes (variabl
