Failed to load the given URL

[bsmither]

I fully understand this - probably.

I am trying to troubleshoot a Tomcat problem, one in which a GET request for an image receives a response of Content-Type "text/html" and the content is the same as the index.html page.

I know this because I see the traffic using Wireshark.

However, in Firebug's Net tab, Firebug does not show what was actually received. (In the not too distant past, I was able to see the 404 response if the image file did not exist.)

Perhaps Firefox is destroying the response if the "Accept: image/png" does match the response "Content-Type: text.html"?

Is there a means to have Firebug show what was actually received, even if Firefox isn't going to put it in the DOM?

[Sebastian Zartner]

What do the Firefox DevTools show? Do you have a public test case, so the issue can be reproduced?

Sebastian

[rishi rajavel]

Hi

--
You received this message because you are subscribed to the Google Groups "Firebug" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firebug+u...@googlegroups.com.
To post to this group, send email to fir...@googlegroups.com.
Visit this group at https://groups.google.com/group/firebug.
To view this discussion on the web visit https://groups.google.com/d/msgid/firebug/3127f72b-1f84-464d-8bbc-42a052e61af5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[bsmither]

I had an example to show, but I accidentally fixed the problem that was to show what I was wanting Firebug to be able to do.

[Sebastian Zartner]

You accidentally fixed the problem? :-) Just wondering, was it an issue in Firebug or related to your page?

Sebastian

[bsmither]

Not technically a Tomcat problem. I had a JAVA coding misunderstanding - since been fixed - that caused Tomcat to send the wrong type of response for what was requested:
Request >> image.jpg
Response >> text/html (but Firebug would not display it)

I would like to see what was Tomcat's Response in Firebug. Discovering the actual content would have likely identified the source of the coding error.

I had posted a publicly accessible site so that you could test with your own Firebug to see what I was referring to. But then I fixed the coding problem, inadvertently, apparently before anyone requested the page.

[Sebastian Zartner]

I tried to access the page you posted before, though it was unfortunately not accessible for me.

But I think I can reproduce your issue with the attached two files. The HTML file has an <img> tag referencing a PHP script, which returns text/html as Content-Type.
This lets Firebug output 'Reload the page to get source for: ...':

So that's obviously a bug. Though in the Headers tab the Content-Type is correctly listed with text/html.
Note that in that case the Firefox and Chrome DevTools also don't display the contents. The Firefox DevTools claim that the response is empty and the Chrome DevTools output "Failed to load response data".
I didn't investigate yet why that's the case, though.

Sebastian