Mozilla Support में खोजें

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Pictures being blocked

  • 6 प्रत्युत्तर
  • 2
  • 1 view
  • के द्वारा अंतिम प्रतियुतर cor-el

more options

When i try to view images i get this angry little emote http://i1252.photobucket.com/albums/hh567/NeonFirecracker/Edits/firefox_zpsdfccbc44.png i have to click him to view images on pages. however i would like to disable him and for the images to load automatically rather than have to click him on every thing image over and over and over again how do i do this?

When i try to view images i get this angry little emote http://i1252.photobucket.com/albums/hh567/NeonFirecracker/Edits/firefox_zpsdfccbc44.png i have to click him to view images on pages. however i would like to disable him and for the images to load automatically rather than have to click him on every thing image over and over and over again how do i do this?

All Replies (6)

more options

That is a problem with the photobucket site. Firefox sends the default HTTP accept header (network.http.accept.default) instead of the image header (image.http.accept) and that makes photobucket redirect to an HTML page with the image embedded.

  • text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
  • image/png,image/*;q=0.8,*/*;q=0.5
more options

Is there a way to fix it? Or make it stop?

more options

I went to Recent Uploads and clicked through randomly and was able to view images. I have some advertising scripts blocked, and Flash blocked; I don't know whether that is relevant.

Can you see this photo:

http://media.photobucket.com/user/pyrrhandork/media/chinaaa/IMG_2819_zps52b4f2b8.jpg.html?filters[recentUploads]=recentUploads&filters[media_type]=image&sort=1&o=25

Any difference if you right-click and choose Open Link in New Private Window?

more options

The point is that the direct picture link isn't working in Firefox. http://i1252.photobucket.com/albums/hh567/NeonFirecracker/Edits/firefox_zpsdfccbc44.png In Firefox you get redirected to an HTML page with the image unless this image is in the cache. http://s1252.photobucket.com/user/NeonFirecracker/media/Edits/firefox_zpsdfccbc44.png.html

In Google Chrome you get the image.

http://i1252.photobucket.com/albums/hh567/NeonFirecracker/Edits/firefox_zpsdfccbc44.png

GET /albums/hh567/NeonFirecracker/Edits/firefox_zpsdfccbc44.png HTTP/1.1
Host: i1252.photobucket.com
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8

HTTP/1.1 302 Moved Temporarily
Content-Length: 227
Content-Type: text/html
Location: http://s1252.photobucket.com/albums/hh567/NeonFirecracker/Edits/firefox_zpsdfccbc44.png

HTTP/1.1 302 Found
Location: http://s1252.photobucket.com/user/NeonFirecracker/media/Edits/firefox_zpsdfccbc44.png.html
Content-Length: 274
Keep-Alive: timeout=3, max=100
Connection: Keep-Alive
Content-Type: text/html; charset=iso-8859-1

If you use the Live Http Headers extension and remove the accept header and click Replay then you get the image

http://i1252.photobucket.com/albums/hh567/NeonFirecracker/Edits/firefox_zpsdfccbc44.png

GET /albums/hh567/NeonFirecracker/Edits/firefox_zpsdfccbc44.png HTTP/1.1
Host: i1252.photobucket.com

HTTP/1.1 200 OK
Cache-Control: max-age=21600
Content-Length: 1985
Content-Type: image/png
more options

cor-el, thank you for clarifying that.

So Firefox will send image-specific accept headers when the image is called by an <img> tag in a page, but when the image is requested directly without that context, it sends general accept headers. (It doesn't take a cue from the file extension.)

If I override Firefox's general default headers with the image headers, then there is no redirect, of course. But that may cause other issues, so it's not an ideal workaround.

Tested:

(1) In a new tab, type or paste about:config in the address bar and press Enter. Click the button promising to be careful.

(2) In the search box above the list, type or paste accept and pause while the list is filtered

(3) Right-click the image.http.accept preference and Copy Value

(4) Double-click the network.http.accept.default preference, delete the existing value, then paste, then click OK

(Simply adding image/*; to the default headers didn't work.)

more options

Yes, setting network.http.accept.default to an empty string works, but is not really an acceptable solution. I had posted that workaround before in older threads about this issue with images on Photobucket.