On Fri, Feb 15, 2008 at 10:39 PM, Andrew2008
<[EMAIL PROTECTED]> wrote:
>
> I just installed Apache and I have the following statements in the httpd.conf
> file. The page is all messed up when I went to http://localhost/foo. You
> can go to www.yamaha.com and see what the page supposes to look
I just installed Apache and I have the following statements in the httpd.conf
file. The page is all messed up when I went to http://localhost/foo. You
can go to www.yamaha.com and see what the page supposes to look like. Below
are what I got from the access_log and error_log. Can you show me h
Now that I'm staring at this. I see that I've a different IP address on
eth0. However, I still get the same error message with
Listen 80
in httpd.conf than if I specified the IP.
mw
--
"Lose not thy airspeed, lest the ground rises up and smites thee."
-- William Kershner
Mike Watson
Here it is...
[EMAIL PROTECTED] ~]# ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:26:54:0E:AD:87
inet addr:192.168.1.30 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::226:54ff:fe0e:ad87/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Ok, how about:
ifconfig -a
Please respond to users@httpd.apache.org
To: users@httpd.apache.org
cc: (bcc: Dan Mitton/YD/RWDOE)
Subject:Re: [EMAIL PROTECTED] HTTPD won't start. Fails with error
message.
LSN: Not Relevant
User Filed as: Not a Record
I fat fingered it when I wro
I fat fingered it when I wrote the e-mail. Here's the LISTEN statement
in httpd
Listen 192.168.1.200:80
In this particular config, I'm not using VirtualHost. They are
commented out. I simplified the config greatly trying to find the problem.
mw
"Lose not thy airspeed lest the ground
You fat fingered it when you cut and pasted from the error log?? What do
your "Listen" and "VirtualHost" directives look like?
Please respond to users@httpd.apache.org
To: users@httpd.apache.org
cc: (bcc: Dan Mitton/YD/RWDOE)
Subject:Re: [EMAIL PROTECTED] HTTPD won't start. F
The same as with 127.0.0.1. Connection refused.
mw
"Lose not thy airspeed lest the ground rises up and smites thee." - Anon.
Richard de Vries wrote:
How about a telnet 192.168.1.300 80
(in case you configured your Apache to only listen on this IP and not on the
loopback device)
- Ori
No. I fat fingered it. It's 192.168.1.200
mw
"Lose not thy airspeed lest the ground rises up and smites thee." - Anon.
PingBad wrote:
192.168.1.300
For the sake of sanity, the IP of the machine you're working on is that IP,
right?
-
Here's the netstat output. There isn't any difference from my other
servers.
netstat -a | grep LISTEN
[EMAIL PROTECTED] ~]# netstat -a | grep LISTEN
tcp0 0 localhost6.localdomai:irdmi *:*
LISTEN
tcp0 0 localhost6.localdomain:2208 *:*
I've checked using lsof and netstat and there's nothing else listening
on port 80.
mw
"Lose not thy airspeed lest the ground rises up and smites thee." - Anon.
Joshua Slive wrote:
On Fri, Feb 15, 2008 at 6:19 PM, Mike - W0TMW <[EMAIL PROTECTED]> wrote:
I'm building a server based on Fed
This is for mod_auth_ldap ?
He means the "proxy" user who does all of the attribute:value looks in
LDAP. Normally the "proxy" user is a "meta" user identity in LDAP --
with limited search functionality and a nice strong password.
Store the password in SHA1+Base64 in the Apache config file.
En
How about a telnet 192.168.1.300 80
(in case you configured your Apache to only listen on this IP and not on the
loopback device)
- Original Message
From: Mike - W0TMW <[EMAIL PROTECTED]>
To: users@httpd.apache.org
Sent: Friday, February 15, 2008 5:37:22 PM
Subject: Re: [EMAIL PROTECTED
> 192.168.1.300
For the sake of sanity, the IP of the machine you're working on is that IP,
right?
--
PingBad,
IRC Fanatic
-
The official User-To-User support forum of the Apache HTTP Server Project.
See http://httpd.apache.org/
How about the output from:
netstat -na | grep LISTEN
How many "Listen" commands do you have in your httpd.conf ?
Please respond to users@httpd.apache.org
To: users@httpd.apache.org
cc: (bcc: Dan Mitton/YD/RWDOE)
Subject:Re: [EMAIL PROTECTED] HTTPD won't start. Fails with err
Connect to address 127.0.0.1 Connection refused.
"Lose not thy airspeed lest the ground rises up and smites thee." - Anon.
Richard de Vries wrote:
It appears something else is already listening on port 80 and as such Apache is
unable to bind to that port.
What happens when you do a "telnet
On Fri, Feb 15, 2008 at 6:19 PM, Mike - W0TMW <[EMAIL PROTECTED]> wrote:
> I'm building a server based on Fedora 7 and httpd won't start. I'm
> running out of space on another server and this one is intended as a
> replacement. I've looked through the archives, FAQs and while this
> issue is m
It appears something else is already listening on port 80 and as such Apache is
unable to bind to that port.
What happens when you do a "telnet localhost 80". Do you get connected?
- Original Message
From: Mike - W0TMW <[EMAIL PROTECTED]>
To: users@httpd.apache.org
Sent: Friday, Februar
On Fri, Feb 15, 2008 at 5:42 PM, Michael McGlothlin
<[EMAIL PROTECTED]> wrote:
>
> >> I'm using PHP to dynamically serve images and am using compression on
> >> the output. For GET I know that I should make the Content-Length header
> >> the size of the compressed data. For HEAD requests do I
I'm building a server based on Fedora 7 and httpd won't start. I'm
running out of space on another server and this one is intended as a
replacement. I've looked through the archives, FAQs and while this
issue is mentioned, that's all I can find---a mention with no help for
resolution.
The e
I'm using PHP to dynamically serve images and am using compression on
the output. For GET I know that I should make the Content-Length header
the size of the compressed data. For HEAD requests do I do the same or
do I provide the uncompressed Content-Length? Thanks.
HEAD responses shoul
On Fri, Feb 15, 2008 at 4:39 PM, Michael McGlothlin
<[EMAIL PROTECTED]> wrote:
> I'm using PHP to dynamically serve images and am using compression on
> the output. For GET I know that I should make the Content-Length header
> the size of the compressed data. For HEAD requests do I do the same or
I'm using PHP to dynamically serve images and am using compression on
the output. For GET I know that I should make the Content-Length header
the size of the compressed data. For HEAD requests do I do the same or
do I provide the uncompressed Content-Length? Thanks.
--
Michael McGlothlin
South
So, is there any way to force a 404 error when someone uses /something ?
You could use mod rewrite or have your script check for it and generate
a 404 error.
--
Michael McGlothlin
Southwest Plumbing Supply
smime.p7s
Description: S/MIME Cryptographic Signature
On Thu, Feb 14, 2008 at 4:05 PM, srikanth V
<[EMAIL PROTECTED]> wrote:
> hi all
>
> i need u r help in configuring http 2.0.60 server
>
>
> i am cognos consultant i wanna install websever for cognos to run on web .i
> wanna create virtual directories , so that i can link tham to my cognos
> folder
On Fri, Feb 15, 2008 at 6:39 AM, john <[EMAIL PROTECTED]> wrote:
> So, is there any way to force a 404 error when someone uses /something ?
Depending on your apache version, see the AccepPathInfo directive.
http://httpd.apache.org/docs/2.2/mod/core.html#acceptpathinfo
Joshua.
---
So, is there any way to force a 404 error when someone uses /something ?
-Original Message-
From: Nick Kew [mailto:[EMAIL PROTECTED]
Sent: Friday, February 15, 2008 1:31 PM
To: users@httpd.apache.org
Subject: Re: [EMAIL PROTECTED] Apache handles filename/something
On Fri, 15 Feb 2008 13
On Fri, 15 Feb 2008 13:26:50 +0200
"john" <[EMAIL PROTECTED]> wrote:
> Hi all
>
> When I type http://server/index.php i can see the index.php
> But when I type http://server/index.php/1234 i can also see the
> index.php
The term you're looking for in TFM is PATH_INFO.
> I assume that Apache han
Hi all
When I type http://server/index.php i can see the index.php
But when I type http://server/index.php/1234 i can also see the index.php
I assume that Apache handles index.php as a directory or alias and does not
give the 404 error code but 304 or 200.
Any thoughts on that?
Yup, you will need to either change the existing httpd init script, or
build a new one from scratch.
You can read here for details on creating new init script:
/usr/share/doc/initscripts-8.45.17.EL/sysvinitfiles(your path
may be different)
Melanie Pfefer wrote:
Hello
I compiled and i
Hello
I compiled and installed 2.0.59 on redhat.
However, /etc/init.d/httpd still points to the old
apache (1.3)
What to change in /etc/init.d/httpd file?
Thanks.
__
Sent from Yahoo! Mail - a smarter inbox http://uk.mail.yahoo.co
31 matches
Mail list logo
