Re: apache mysterious 404 error

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]



What is the absolute path on the server that /mycompanyStore/images/ is store in?

-----Original Message-----
From: centos-bounces@xxxxxxxxxx [mailto:centos-bounces@xxxxxxxxxx] On Behalf Of Tim Dunphy
Sent: Friday, August 28, 2015 10:12 AM
To: CentOS mailing list <centos@xxxxxxxxxx>
Subject: Re:  apache mysterious 404 error

Hey guys,

 Sorry for the failed attempts at obscuring the company I work for. My boss wouldn't take too kindly to it if I revealed that information on a mailing list. :)

So anyway, I realized that capitalization might be the problem. So I renamed the directory to match what was in the URL. That didn't solve the problem.

However I noticed this message turning up in the logs:

[Fri Aug 28 01:27:30.057020 2015] [proxy:warn] [pid 23782:tid 139661984888576] [client 173.213.212.234:14579] AH01144: No protocol handler was valid for the URL /mycompanyStore/images/Jimmy_792x802_R2.jpg.
If you are using a DSO version of mod_proxy, make sure the proxy submodules are included in the configuration using LoadModule., referer:
http://stage.theshopatmycompanystudios.com/

[Fri Aug 28 01:27:30.057216 2015] [proxy:warn] [pid 23780:tid 139661995378432] [client 173.213.212.234:14577] AH01144: No protocol handler was valid for the URL /mycompanyStore/images/Jimmy_485x1215_R2.jpg.
If you are using a DSO version of mod_proxy, make sure the proxy submodules are included in the configuration using LoadModule., referer:
http://stage.theshopatmycompanystudios.com/

[Fri Aug 28 01:27:43.377172 2015] [proxy:warn] [pid 23890:tid 139661827540736] [client 173.213.212.234:2425] AH01144: No protocol handler was valid for the URL /mycompanyStore/images/altImg.png. If you are using a DSO version of mod_proxy, make sure the proxy submodules are included in the configuration using LoadModule., referer:
http://stage.theshopatmycompanystudios.com/

[Fri Aug 28 01:27:43.377269 2015] [proxy:warn] [pid 23889:tid 139661942929152] [client 173.213.212.234:2426] AH01144: No protocol handler was valid for the URL /mycompanyStore/images/Jimmy_485x1215_R2.jpg. If you are using a DSO version of mod_proxy, make sure the proxy submodules are included in the configuration using LoadModule., referer:
http://stage.theshopatmycompanystudios.com/

[Fri Aug 28 01:27:43.377384 2015] [proxy:warn] [pid 23889:tid 139661953419008] [client 173.213.212.234:2427] AH01144: No protocol handler was valid for the URL /mycompanyStore/images/Jimmy_792x802_R2.jpg. If you are using a DSO version of mod_proxy, make sure the proxy submodules are included in the configuration using LoadModule., referer:
http://stage.theshopatmycompanystudios.com/

[Fri Aug 28 01:27:43.382079 2015] [proxy:warn] [pid 23891:tid 139662047827712] [client 173.213.212.234:2430] AH01144: No protocol handler was valid for the URL /mycompanyStore/images/Jimmy_792x413_R2.jpg. If you are using a DSO version of mod_proxy, make sure the proxy submodules are included in the configuration using LoadModule., referer:
http://stage.theshopatmycompanystudios.com/

[Fri Aug 28 01:28:01.750944 2015] [proxy:warn] [pid 23977:tid 139661911459584] [client 173.213.212.234:6011] AH01144: No protocol handler was valid for the URL /mycompanyStore/images/altImg.png. If you are using a DSO version of mod_proxy, make sure the proxy submodules are included in the configuration using LoadModule., referer:
http://stage.theshopatmycompanystudios.com/

[Fri Aug 28 01:28:01.751086 2015] [proxy:warn] [pid 23978:tid 139662016358144] [client 173.213.212.234:6013] AH01144: No protocol handler was valid for the URL /mycompanyStore/images/Jimmy_485x1215_R2.jpg. If you are using a DSO version of mod_proxy, make sure the proxy submodules are included in the configuration using LoadModule., referer:
http://stage.theshopatmycompanystudios.com/

[Fri Aug 28 01:28:01.755018 2015] [proxy:warn] [pid 23977:tid 139661890479872] [client 173.213.212.234:6012] AH01144: No protocol handler was valid for the URL /mycompanyStore/images/Jimmy_792x413_R2.jpg. If you are using a DSO version of mod_proxy, make sure the proxy submodules are included in the configuration using LoadModule., referer:
http://stage.theshopatmycompanystudios.com/

[Fri Aug 28 01:28:01.755120 2015] [proxy:warn] [pid 23978:tid 139662005868288] [client 173.213.212.234:6014] AH01144: No protocol handler was valid for the URL /mycompanyStore/images/Jimmy_792x802_R2.jpg. If you are using a DSO version of mod_proxy, make sure the proxy submodules are included in the configuration using LoadModule., referer:
http://stage.theshopatmycompanystudios.com/


So taking the advice of that eror I tried enabling all the proxy modules in the apache config:


LoadModule proxy_module modules/mod_proxy.so

LoadModule proxy_connect_module modules/mod_proxy_connect.so

LoadModule proxy_ftp_module modules/mod_proxy_ftp.so

LoadModule proxy_http_module modules/mod_proxy_http.so

LoadModule proxy_fcgi_module modules/mod_proxy_fcgi.so


But those files are still 404ing. Not sure where to take it from here. I'd appreciate any help you can give!


Thanks

On Fri, Aug 28, 2015 at 10:00 AM, Robert Wolfe <Robert.Wolfe@xxxxxxxxx>
wrote:

> Check the links again.  Remove the * from images*/ and you should be 
> all set.
>
> -----Original Message-----
> From: centos-bounces@xxxxxxxxxx [mailto:centos-bounces@xxxxxxxxxx] On 
> Behalf Of Tim Dunphy
> Sent: Thursday, August 27, 2015 5:18 PM
> To: CentOS mailing list <centos@xxxxxxxxxx>
> Subject:  apache mysterious 404 error
>
> Hey guys,
>
>  Just have a question about apache. Hoping to get an opinion on this.
>
>  I've just setup a site under apache 2.4.
>
>  And made sure that the document root setup in the vhost for the site 
> I'm serving has permissions for the apache user. Yet some of the files 
> are throwing a 404 error in a browser even tho they are clearly 
> present and accounted for on the file system.
>
> For example, I'm getting this error:
>
> (index):1 GET
> http://stage.theshopatmycomany.com/mycomanyStore/images*/altImg.png
> 404 (*Not Found)
>
> (index):1 GET
> http://stage.theshopatmycomany.com/mycomanyStore/images*/Jimmy_485x121
> 5_R2.jpg
> 404* (Not Found)
>
> (index):1 GET
> http://stage.theshopatmycomany.com/mycomanyStore/images*/Jimmy_792x802
> _R2.jpg
> 404* (Not Found)
>
> (index):1 GET
> http://stage.theshopatmycomany.com/mycomanyStore/images*/Jimmy_792x413
> _R2.jpg
> 404* (Not Found)
> And yet as I mentioned all those files are definitely there on the 
> file
> system:
>
> [root@aozwsls00019la apache2]# ls -l
> /var/www/mycomanystore/images/altImg.png
> /var/www/mycomanystore/images/Jimmy_485x1215_R2.jpg
> /var/www/mycomanystore/images/Jimmy_792x802_R2.jpg
> /var/www/mycomanystore/images/Jimmy_792x413_R2.jpg
>
> -rw-r--r--. 1 daemon daemon    128 Aug 27 12:22
> /var/www/mycomanystore/images/altImg.png
>
> -rw-r--r--. 1 daemon daemon 260983 Jul 16 14:03 
> /var/www/mycomanystore/images/Jimmy_485x1215_R2.jpg
>
> -rw-r--r--. 1 daemon daemon 126628 Jul 16 14:00 
> /var/www/mycomanystore/images/Jimmy_792x413_R2.jpg
>
> -rw-r--r--. 1 daemon daemon 222568 Jul 16 13:56 
> /var/www/mycomanystore/images/Jimmy_792x802_R2.jpg
>
> And all those files have the correct ownership for apache:
>
> [root@aozwsls00019la apache2]# egrep -i "user|group" conf/httpd.conf | 
> egrep -i -v -e '#' -e log -e module
>
> User daemon
>
> Group daemon
>
> All the files are owned by daemon:daemon!! So why on earth are these 
> files giving a 404?
>
> This is my virtual host for the site:
>
>
> <VirtualHost *>
>
>     ServerAdmin timothy.dunphy@xxxxxxxxxxxx
>
>     DocumentRoot /var/www/mycomanystore
>
>     ServerName stage.theshopatmycomanystudios.com
>
>     ServerAlias 173.213.219.48
>
>     ErrorLog logs/store_error_log
>
>     LogFormat "%h %l %u %t \"%r\" %>s %b" common
>
>     CustomLog logs/store_access_log common
>
>     <Directory /var/www/mycomanystore>
>
>       DirectoryIndex index.html
>
>       AddHandler cgi-script .cgi
>
>       Options -Indexes +FollowSymLinks +ExecCGI +Includes
>
>       AllowOverride All
>
>       Require all granted
>
>     </Directory>
>
>     ExpiresActive On
>
>     ExpiresDefault "access plus 30 minute"
>
>     RewriteEngine On
>
>     RewriteCond %{REQUEST_METHOD} ^TRACE
>
>     RewriteRule .* - [F]
>
> </VirtualHost>
>
> Thanks
>
> Tim
>
>
> --
> GPG me!!
>
> gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B 
> _______________________________________________
> CentOS mailing list
> CentOS@xxxxxxxxxx
> https://lists.centos.org/mailman/listinfo/centos
> _______________________________________________
> CentOS mailing list
> CentOS@xxxxxxxxxx
> https://lists.centos.org/mailman/listinfo/centos
>



--
GPG me!!

gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B _______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
https://lists.centos.org/mailman/listinfo/centos
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
https://lists.centos.org/mailman/listinfo/centos



[Index of Archives]     [CentOS]     [CentOS Announce]     [CentOS Development]     [CentOS ARM Devel]     [CentOS Docs]     [CentOS Virtualization]     [Carrier Grade Linux]     [Linux Media]     [Asterisk]     [DCCP]     [Netdev]     [Xorg]     [Linux USB]
  Powered by Linux