GNOME Bugzilla – Bug 168554
Choosing "Save Image As..." will download the image again
Last modified: 2007-04-25 08:43:15 UTC
Please describe the problem: When right (context) clicking on image and choosing "Save Image As..." from the menu, the image will be re-downloaded again, not fetched from the cache as it should be. This especially happens with large images. Steps to reproduce: 1. Visit http://machall.com (as an example) 2. Context click on the image (comic strip) and chose "Save Image As..." 3. Save the image in any location you like Actual results: Re-downloading the image again. Expected results: Fetching the image from the cache. Does this happen every time? Yes. Other information: Is this related to <a href=http://bugzilla.gnome.org/show_bug.cgi?id=141652>bug #141652</a>?
Sorry for the double post (I should have wrote this in the first post). UbuntuLinux 5.04 "Hoary", Linux 2.6.10-4-k7, Gnome 2.9.9x, Epiphany 1.5.6 (package epiphany-browser_1.5.6-0ubuntu1_i386.deb, using mozilla-firefox_1.0+dfsg.1-6ubuntu1_i386.deb). Typing "about:" in the address bar gives: "Firefox 1.0 Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20050221 Epiphany/1.5.6 (Ubuntu) (Ubuntu package 1.0+dfsg.1-6ubuntu1)" This same problem exist in Epiphany 1.4.6 (Debian Unstable package: epiphany-browser_1.4.6-1_i386.deb using Mozilla package: mozilla-browser_1.7.3-5_i386.deb). This problem does *NOT* exist in Firefox 1.0. The server hosting the image dose not send any HTTP-Headers that affect the caching of the image (ie. no Expires, Cache-Control, or ETag header(s)). By browsing "~/.gnome2/epiphany/mozilla/epiphany/Cache", it seems there are far few files than the cache of Firefox even after clearing the cache and then visiting the same locations on both browsers.
I cannot reproduce this here (using epiphany HEAD with firefox trunk backend). Bug 141652 only applies for saving web pages including images, not for saving an image by itself.
May be it's fixed in Epiphany HEAD, or may be you have a *VERY* fast connection that you did not notice (did you try monitoring the TCP traffic or try it in a slow (i.e. dial-up) connection (sorry, but I had to ask!))?!. I'll wait for the next Epiphany release and try again.
I made a test site, and changed the image on the server after loading the page and befores saving the image. It saved the image as displayed not as now-on-server.
Again, and totally my fault (I'm really sorry), I forgot to mention that I'm using (actually, forced to use) a proxy! Might this the reason you could not reproduce the problem (or even the cause of the problem itself)?
Reporter, do you still see this problem?
> Reporter, do you still see this problem? Sadly, yes. Now I'm using Epiphany 1.6.1 (package name: epiphany-browser_1.6.1-0ubuntu2_i386.deb) with Firefox 1.0.2 back-end (with appropriate security patches from Ubuntu, package name: mozilla-firefox_1.0.2-0ubuntu5.3_i386.deb). Typing "about:" in the URL bar gives me: "Firefox 1.0.2" "Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050524 Epiphany/1.6.1 (Ubuntu) (Ubuntu package 1.0.2 MFSA2005-44)" I found out that my ISP's proxy I'm using goes through another proxy! I don't know if this cause the problem, but as I said before, this does *not* happen in Firefox! I found a solution by installing a proxy "Polipo" on my system and using it for Epiphany which solve the problem for me (Okay, this is not a *real* solution, but it's enough for me). Thanks.
We now try harder to get a cache entry for the content, but still cannot guarantee that there is one. Anyway
(pressed return too early) Anyway, this is the best we can do for 1.8.0, but leaving open for further consideration.
Still happens. You can confirm against any "captcha" image (like the ones in blog comments).
Currently, I'm using ArchLinux.org, and Epiphany's "about:" gives: --------------- Epiphany 2.16.1 Mozilla/5.0 (X11; U; Linux i686; en; rv:1.8.0.7) Gecko/20060924 Epiphany/2.16 --------------- And yes, it still happens. I just checked with "machall.com". My ISP's proxy is an "HTTP 1.0" with "Persistent Connection" enabled, "Pipeline" disabled, and "Max Connection" allowed is 2 (if that matters). Thank you all for your trouble.
*** This bug has been marked as a duplicate of 141652 ***