| Re: totally WEIRD bug? Firefox caching? [message #185368 is a reply to message #185366] |
Thu, 20 March 2014 12:43   |
Jerry Stuckle
Messages: 2598
Registered: September 2010
Karma:
|
Senior Member |
|
|
On 3/20/2014 7:26 AM, The Natural Philosopher wrote:
> On 20/03/14 09:13, Arno Welzel wrote:
>> Am 19.03.2014 18:25, schrieb The Natural Philosopher:
>>
>>> I have TWO IDENTICAL PHP FILES.
>>>
>>> They are supposed to display an image got from a database.
>>>
>>> One does. The other does not.
>>>
>>> It persistently tells me the image is corrupted.
>>>
>>> I have even copied one file that works directly over the other. It still
>>> doesn't work.
>>>
>>>
>>> I have debugged it, got it to output the image to a file and read the
>>> file successfully.
>>
>> What means "read successfully"? Is it a valid image? Is the response
>> from the server valid?
>
> Thanks for all the replies because finally I found a permissions
> difference and although I dont completely understand why it is
> happening, I know WHAT is happening.
>
> What is happning - and oddly running it against a test version of IE6 in
> my XP VM showed it up, was that it was outputting a '404 file not found'
> text BEFORE outputting perfectly valid PNG.
>
> Why this is happening is a bug somewhere else completely.
>
> IE 6 simply showed the text and the binary gobbledygook which was the
> clue I needed.
>
> How this has happened will take me some time to understand because the
> line that says '404 not found' is followed - or I thought it was - by
> an exit(); statement.
>
>> Either Firefox once got an invalid image and cached the response or the
>> server does not respond the way you think. Maybe a BOM in the PHP file?
>> This may not be visible in your editor, but it can cause all sort of
>> problems.
>>
>>
> Firefox makes it hard to debug because it DOES cache bad results: I
> usually fix that by sending random nonsensical GET parameters which are
> ignored to ensure it thinks its a different URL each time.
>
> It a huge minus against firefox that it didn't - even using the
> debugging console - show me what was really going on, whereas IE6 did.
>
>
Firefox with the web developer extensions will show you EXACTLY what's
going on. But you have to know enough to understand the request and
response headers.
Additionally, you can just clear the cache in Firefox. It's quite easy
to do.
--
==================
Remove the "x" from my email address
Jerry Stuckle
jstucklex(at)attglobal(dot)net
==================
|
|
|
|
Calendar
Search
Help
Members
Register
Login
Home
]