Displaying 6 results from an estimated 6 matches for "ah01144".
2015 Aug 28
4
apache mysterious 404 error
...hat 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 Aug 28
1
apache mysterious 404 error
...roblem. 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/
>
>...
2015 Aug 28
0
apache mysterious 404 error
...hat 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 Aug 27
7
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,
2015 Aug 28
0
apache mysterious 404 error
...blem. 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/
>
>...
2015 Aug 28
2
apache mysterious 404 error
...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.theshopatmycomp...