|
Home > Archive > Apache Server configuration support > November 2006 > Linux Apache2 php X-File Issue - I have no Idea please Help
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Linux Apache2 php X-File Issue - I have no Idea please Help
|
|
| Christian Meier 2006-11-22, 1:18 pm |
| Hi Folks
I am running a Debian Server with Apache2.0 and php4. I had a total
Systemcrasch and after recovery there ist a real mystic issue. When i=CD
surf trough the www (not internal LAN) everything looks allright. It
dos not matter if I surf with Internetexplorer or FireFox. But some
Friends cannot surf trough Firefox because the Browser downloads the
php-source. If they use Internetexplorer ist OK. When they type the
complete URL in Firefox ist also OK. For example webmail.thedomail.biz
dont work. http://webmail.consult-it.biz/src/login.php works.
I have no Idea is the Problem at Apache? But on my Machine everything
works as expected. Is it a Client Problem? but they have had just run
setup.exe non special setting in their browsers???
Any Ideas??? I am really stumbled??
THX
Christian Meier
| |
| shimmyshack 2006-11-22, 7:23 pm |
| do you have any rewrites based on useragent which force the mime-type
to be something other than that usually reserved for display by
firefox?
ReWriteCond firefox
ReWriteRule . /path/somefile.php [T=application/octet]
_IF_ it true that the source of the php is revealed then you DO have a
problem with your server,
AddType application/octet .php
would also acheive the same thing.
grep for application in your conf files.
could it be that only the php page is executed and the html is
downloaded? that would imply another setup issue. Either way it does
appear you have an issue with a conf file related to user-agent.
What happens if you change Firefox's user agent to
Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)
using user agent switcher?
https://addons.mozilla.org/firefox/59/
| |
| Christian Meier 2006-11-24, 7:25 am |
| Thank You!
> do you have any rewrites based on useragent which force the mime-type
> to be something other than that usually reserved for display by
> firefox?
> ReWriteCond firefox
> ReWriteRule . /path/somefile.php [T=application/octet]
Hmmm .... I don't use the Browser in any way of my config File
> _IF_ it true that the source of the php is revealed then you DO have a
> problem with your server,
Thats why I thougt I post in the Apache Forum
>
> AddType application/octet .php
> would also acheive the same thing.
Since I canged to application/octet and back to AddType
application/x-httpd-php .php .phtml .php3 my Firefox have the same
Problem. IE is still OK ...
> What happens if you change Firefox's user agent to
> Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)
> using user agent switcher?
> https://addons.mozilla.org/firefox/59/
Same result, source gets downloaded in all user agents
The Issue is in the Forwarding php's like squirrel or wikipedia uses.
If they who have Problems type the whole URL everything is OK.
I do not know what this could be ...
| |
| shimmyshack 2006-11-24, 7:25 am |
| I keep wondering what you mean by the php source? can you be clear, do
you actually mean that, as in
<?php echo 'blah...'; ?>
if you can confirm this I am out of ideas, your php isnt being
processed serverside,
the reason I mentioned user_agent or mime types was because thats the
only way that the request differs between browsers.
My first thought was that in fact it wasnt the php source, but just a
forced download of the html, which can happen as a result of the
headers - interpreted differently between firefox and ie.
My only suggestion - if it is NOT the actual php source -is that you
download fiddlertool - a freeware proxy from microsoft, or use
something like wirehsark on linux, to actually see what headers are
being returned.
If it is - see how hard time I am having believing it is - I am out of
ideas that dont involve the browser user_agent cos thats the only way
they differ, the rest is just oridnary stuff. It is so much more likely
to be the response headers that are tripping up firefox, and that
implies the php is executing as required and there should be no source
inside the page when inspected.
The forwrding thing should result in php code in both browsers if it
does in one. Hmm..
|
|
|
|
|