[EMAIL PROTECTED] HTTP Server 2.2.9 - Unable to view the files from IE
Hello Edward, Thank you for your reply. Was able to see your reply in the archives but it didn't land in my inbox yet. Subscribed to this list just a moment before posting this question. So, it may take a while for the list to reflect my user id as well. So, this may appear as a new thread. Coming back to the original problem, as it didn't work with the default conf file, I made minor modification as below: Original entry: Options FollowSymLinks AllowOverride None Order deny,allow Deny from all Updated as: Options FollowSymLinks AllowOverride None Order allow,deny Allow from all Thank You.
[EMAIL PROTECTED] HTTP Server 2.2.9 - Unable to view the files from IE
Hello Linux Version : Red Hat Enterprise Version 5.0 Downloaded HTTP server 2.2.9 source, built & installed Started the server using the command apachectl start & the server started fine. No errors in logs/error_log Have attached httpd.conf >From the IE in my windows box, if I access the URL, http://a.b.c.d get the >error message that, "Page Not Found" >From my windows system, am able to ping linux server a.b.c.d Could someone please explain, what to look for and how to solve this problem ? Thanks # # This is the main Apache HTTP server configuration file. It contains the # configuration directives that give the server its instructions. # See http://httpd.apache.org/docs/2.2> for detailed information. # In particular, see # http://httpd.apache.org/docs/2.2/mod/directives.html> # for a discussion of each configuration directive. # # Do NOT simply read the instructions in here without understanding # what they do. They're here only as hints or reminders. If you are unsure # consult the online docs. You have been warned. # # Configuration and logfile names: If the filenames you specify for many # of the server's control files begin with "/" (or "drive:/" for Win32), the # server will use that explicit path. If the filenames do *not* begin # with "/", the value of ServerRoot is prepended -- so "logs/foo_log" # with ServerRoot set to "/usr/local/fnmt/apache2" will be interpreted by the # server as "/usr/local/fnmt/apache2/logs/foo_log". # # ServerRoot: The top of the directory tree under which the server's # configuration, error, and log files are kept. # # Do not add a slash at the end of the directory path. If you point # ServerRoot at a non-local disk, be sure to point the LockFile directive # at a local disk. If you wish to share the same ServerRoot for multiple # httpd daemons, you will need to change at least LockFile and PidFile. # ServerRoot "/usr/local/fnmt/apache2" # # Listen: Allows you to bind Apache to specific IP addresses and/or # ports, instead of the default. See also the # directive. # # Change this to Listen on specific IP addresses as shown below to # prevent Apache from glomming onto all bound IP addresses. # #Listen 12.34.56.78:80 Listen 80 # # Dynamic Shared Object (DSO) Support # # To be able to use the functionality of a module which was built as a DSO you # have to place corresponding `LoadModule' lines at this location so the # directives contained in it are actually available _before_ they are used. # Statically compiled modules (those listed by `httpd -l') do not need # to be loaded here. # # Example: # LoadModule foo_module modules/mod_foo.so # # # If you wish httpd to run as a different user or group, you must run # httpd as root initially and it will switch. # # User/Group: The name (or #number) of the user/group to run httpd as. # It is usually good practice to create a dedicated user and group for # running httpd, as with most system services. # User daemon Group daemon # 'Main' server configuration # # The directives in this section set up the values used by the 'main' # server, which responds to any requests that aren't handled by a # definition. These values also provide defaults for # any containers you may define later in the file. # # All of these directives may appear inside containers, # in which case these default settings will be overridden for the # virtual host being defined. # # # ServerAdmin: Your address, where problems with the server should be # e-mailed. This address appears on some server-generated pages, such # as error documents. e.g. [EMAIL PROTECTED] # ServerAdmin [EMAIL PROTECTED] # # ServerName gives the name and port that the server uses to identify itself. # This can often be determined automatically, but we recommend you specify # it explicitly to prevent problems during startup. # # If your host doesn't have a registered DNS name, enter its IP address here. # #ServerName www.example.com:80 # # DocumentRoot: The directory out of which you will serve your # documents. By default, all requests are taken from this directory, but # symbolic links and aliases may be used to point to other locations. # DocumentRoot "/usr/local/fnmt/apache2/htdocs" # # Each directory to which Apache has access can be configured with respect # to which services and features are allowed and/or disabled in that # directory (and its subdirectories). # # First, we configure the "default" to be a very restrictive set of # features. # Options FollowSymLinks AllowOverride None Order allow,deny Allow from all # # Note that from this point forward you must specifically allow # particular features to be enabled - so if something's not working as # you might expect, make sure that you have specifically enabled it # below. # # # This should be changed to whatever you set DocumentRoot to. # # # Possible values for the Options directive are "None", "All", # or any combination of: # Ind
Re: [EMAIL PROTECTED] HTTP Server 2.2.9 - Unable to view the files from IE
Dear Jay, Are you running your web server by using default config file for testing ? Edward. Jay wrote: > Hello > Linux Version : Red Hat Enterprise Version 5.0 > Downloaded HTTP server 2.2.9 source, built & installed > Started the server using the command apachectl start & the server > started fine. No errors in logs/error_log > Have attached httpd.conf > From the IE in my windows box, if I access the URL, http://a.b.c.d get > the error message that, "Page Not Found" > From my windows system, am able to ping linux server a.b.c.d > Could someone please explain, what to look for and how to solve this > problem ? > Thanks > > > > ># ># This is the main Apache HTTP server configuration file. It contains the ># configuration directives that give the server its instructions. ># See http://httpd.apache.org/docs/2.2> for detailed information. ># In particular, see ># http://httpd.apache.org/docs/2.2/mod/directives.html> ># for a discussion of each configuration directive. ># ># Do NOT simply read the instructions in here without understanding ># what they do. They're here only as hints or reminders. If you are unsure ># consult the online docs. You have been warned. ># ># Configuration and logfile names: If the filenames you specify for many ># of the server's control files begin with "/" (or "drive:/" for Win32), the ># server will use that explicit path. If the filenames do *not* begin ># with "/", the value of ServerRoot is prepended -- so "logs/foo_log" ># with ServerRoot set to "/usr/local/fnmt/apache2" will be interpreted by the ># server as "/usr/local/fnmt/apache2/logs/foo_log". > ># ># ServerRoot: The top of the directory tree under which the server's ># configuration, error, and log files are kept. ># ># Do not add a slash at the end of the directory path. If you point ># ServerRoot at a non-local disk, be sure to point the LockFile directive ># at a local disk. If you wish to share the same ServerRoot for multiple ># httpd daemons, you will need to change at least LockFile and PidFile. ># >ServerRoot "/usr/local/fnmt/apache2" > ># ># Listen: Allows you to bind Apache to specific IP addresses and/or ># ports, instead of the default. See also the ># directive. ># ># Change this to Listen on specific IP addresses as shown below to ># prevent Apache from glomming onto all bound IP addresses. ># >#Listen 12.34.56.78:80 >Listen 80 > ># ># Dynamic Shared Object (DSO) Support ># ># To be able to use the functionality of a module which was built as a DSO you ># have to place corresponding `LoadModule' lines at this location so the ># directives contained in it are actually available _before_ they are used. ># Statically compiled modules (those listed by `httpd -l') do not need ># to be loaded here. ># ># Example: ># LoadModule foo_module modules/mod_foo.so ># > > > ># ># If you wish httpd to run as a different user or group, you must run ># httpd as root initially and it will switch. ># ># User/Group: The name (or #number) of the user/group to run httpd as. ># It is usually good practice to create a dedicated user and group for ># running httpd, as with most system services. ># >User daemon >Group daemon > > > > ># 'Main' server configuration ># ># The directives in this section set up the values used by the 'main' ># server, which responds to any requests that aren't handled by a ># definition. These values also provide defaults for ># any containers you may define later in the file. ># ># All of these directives may appear inside containers, ># in which case these default settings will be overridden for the ># virtual host being defined. ># > ># ># ServerAdmin: Your address, where problems with the server should be ># e-mailed. This address appears on some server-generated pages, such ># as error documents. e.g. [EMAIL PROTECTED] ># >ServerAdmin [EMAIL PROTECTED] > ># ># ServerName gives the name and port that the server uses to identify itself. ># This can often be determined automatically, but we recommend you specify ># it explicitly to prevent problems during startup. ># ># If your host doesn't have a registered DNS name, enter its IP address here. ># >#ServerName www.example.com:80 > ># ># DocumentRoot: The directory out of which you will serve your ># documents. By default, all requests are taken from this directory, but ># symbolic links and aliases may be used to point to other locations. ># >DocumentRoot "/usr/local/fnmt/apache2/htdocs" > ># ># Each directory to which Apache has access can be configured with respect ># to which services and features are allowed and/or disabled in that ># directory (and its subdirectories). ># ># First, we configure the "default" to be a very restrictive set of ># features. ># > >Options FollowSymLinks >AllowOverride None >Order allow,deny >Allow from all > > ># ># Note that from this point forward you must specifically allow ># particular features to be
Re: [EMAIL PROTECTED] HTTP Server 2.2.9 - Unable to view the files from IE
Jay wrote: > Hello Edward, > Thank you for your reply. Was able to see your reply in the archives > but it didn't land in my inbox yet. Subscribed to this list just a > moment before posting this question. So, it may take a while for the > list to reflect my user id as well. > So, this may appear as a new thread. > Coming back to the original problem,as it didn't work with the default > conf file, I made minor modification as below: > Original entry: > > Options FollowSymLinks > AllowOverride None > Order deny,allow > Deny from all > > > Updated as: > > Options FollowSymLinks > AllowOverride None > Order allow,deny > Allow from all > > > Thank You. > > Hello Jay, Would you capture your problem as gif/jpg, then post here for discrib your problem ? OR You may try these ( default of FC6 System ) : Options Indexes Includes FollowSymLinks MultiViews ExecCGI Thanks ! Edward.
Re: [EMAIL PROTECTED] HTTP Server 2.2.9 - Unable to view the files from IE
--- On Sun, 9/7/08, Jay <[EMAIL PROTECTED]> wrote: From: Jay <[EMAIL PROTECTED]> Subject: Re: [EMAIL PROTECTED] HTTP Server 2.2.9 - Unable to view the files from IE To: users@httpd.apache.org Date: Sunday, September 7, 2008, 8:56 AM --- On Sun, 9/7/08, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: From: [EMAIL PROTECTED] <[EMAIL PROTECTED]> Subject: Re: [EMAIL PROTECTED] HTTP Server 2.2.9 - Unable to view the files from IE To: users@httpd.apache.org Date: Sunday, September 7, 2008, 8:52 AM Jay wrote: Hello Edward, Thank you for your reply. Was able to see your reply in the archives but it didn't land in my inbox yet. Subscribed to this list just a moment before posting this question. So, it may take a while for the list to reflect my user id as well. So, this may appear as a new thread. Coming back to the original problem, as it didn't work with the default conf file, I made minor modification as below: Original entry: Options FollowSymLinks AllowOverride None Order deny,allow Deny from all Updated as: Options FollowSymLinks AllowOverride None Order allow,deny Allow from all Thank You. Hello Jay, Would you capture your problem as gif/jpg, then post here for discrib your problem ? OR You may try these ( default of FC6 System ) : Options Indexes Includes FollowSymLinks MultiViews ExecCGI Thanks ! Edward. Hello Edward, Have attached the snapshot of the error in the IE. Please let me know, if you need more details. Thanks Hello Edward, The problem was solved, when I disabled the iptables Thank You for your help.
Re: [EMAIL PROTECTED] HTTP Server 2.2.9 - Unable to view the files from IE
Jay, points to the actual '/' path. It is locked down for security reasons, and you should not alter it. To allow access to your server, you should create or alter the block in your virtual host instead. Look out for the DocumentRoot directive to know what path to use. Frank. On Sun, Sep 7, 2008 at 8:38 AM, Jay <[EMAIL PROTECTED]> wrote: > Hello Edward, > > Thank you for your reply. Was able to see your reply in the archives but it > didn't land in my inbox yet. Subscribed to this list just a moment before > posting this question. So, it may take a while for the list to reflect my > user id as well. > > So, this may appear as a new thread. > > Coming back to the original problem, as it didn't work with the default conf > file, I made minor modification as below: > > Original entry: > > > Options FollowSymLinks > AllowOverride None > Order deny,allow > Deny from all > > > > > Updated as: > > > Options FollowSymLinks > AllowOverride None > Order allow,deny > Allow from all > > > > Thank You. > - The official User-To-User support forum of the Apache HTTP Server Project. See http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: [EMAIL PROTECTED] " from the digest: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [EMAIL PROTECTED] HTTP Server 2.2.9 - Unable to view the files from IE
Frank Many thanks for the reply. Have reverted the changes. Thanks again. --- On Sun, 9/7/08, Francois Gingras <[EMAIL PROTECTED]> wrote: From: Francois Gingras <[EMAIL PROTECTED]> Subject: Re: [EMAIL PROTECTED] HTTP Server 2.2.9 - Unable to view the files from IE To: users@httpd.apache.org, [EMAIL PROTECTED] Date: Sunday, September 7, 2008, 2:34 PM Jay, points to the actual '/' path. It is locked down for security reasons, and you should not alter it. To allow access to your server, you should create or alter the block in your virtual host instead. Look out for the DocumentRoot directive to know what path to use. Frank. On Sun, Sep 7, 2008 at 8:38 AM, Jay <[EMAIL PROTECTED]> wrote: > Hello Edward, > > Thank you for your reply. Was able to see your reply in the archives but it > didn't land in my inbox yet. Subscribed to this list just a moment before > posting this question. So, it may take a while for the list to reflect my > user id as well. > > So, this may appear as a new thread. > > Coming back to the original problem, as it didn't work with the default conf > file, I made minor modification as below: > > Original entry: > > > Options FollowSymLinks > AllowOverride None > Order deny,allow > Deny from all > > > > > Updated as: > > > Options FollowSymLinks > AllowOverride None > Order allow,deny > Allow from all > > > > Thank You. > - The official User-To-User support forum of the Apache HTTP Server Project. See http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: [EMAIL PROTECTED] " from the digest: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [EMAIL PROTECTED] HTTP Server 2.2.9 - Unable to view the files from IE
On Sun, Sep 07, 2008 at 06:46:54AM -0700, Jay wrote: > Hello Edward, > > The problem was solved, when I disabled the iptables > > Thank You for your help. Good catch. Glad I read to the current end of thread, to see that you located the issue I was going to suggest. Of course, you don't want to stand naked and vulnerable for too long. Allow queries to destination port 80 on INPUT, and replies, and then turn iptables back on. -- /*\ ** ** Joe Yao [EMAIL PROTECTED] - Joseph S. D. Yao ** \*/ - The official User-To-User support forum of the Apache HTTP Server Project. See http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: [EMAIL PROTECTED] " from the digest: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
