How to view a page with HTTPS images offline in chromium

How to view a page with HTTPS images offline in chromium.
$ chromium http://code.google.com/apis/chart/image/docs/gallery/line_charts.html
Left click first broken image icon and view in new tab.
Click "Proceed anyway".
Now refresh line_charts.html.
This must be done each time you want to view the page.

wwwoffle to be removed from Debian unless a new maintainer steps forth

Gentlemen, wwwoffle is in danger of being removed from Debian
http://news.gmane.org/group/gmane.linux.debian.devel.general/thread=166494/
unless a new maintainer steps forth.
(Me? I'm too old. http://www.youtube.com/watch?v=Kq5WPkLCAiY&list=PL6E40919035151385 )
It would perhaps be quite simple to maintain if one just used pretty
much the official upstream package without any local add ons.

website broken with wwwoffle

Hello,

when I'm trying to fetch 
http://www.hokej-megacamp.sk/hokej-sen/hokej.html
using wwwoffle, I get broken content:

GET http://www.hokej-megacamp.sk/hokej-sen/hokej.html HTTP/1.0

HTTP/1.0 200 OK
Date: Thu, 28 Apr 2011 17:10:23 GMT
Server: Apache
Last-Modified: Mon, 27 Dec 2010 14:32:01 GMT
ETag: "2cd148-2a44-4986532f6da40"
Accept-Ranges: bytes
Content-Type: text/html
Connection: close
Proxy-Connection:
close

!<h<h<m<t</<m<m<m<m<m<l</<b<t<t<t<i</<t<t<t<t<a<i</</</<t<t</</<t<t<t<t<t</</<t<t</<t<a</<a</<a</<a</<a</<a</</<t</</</</</</</<t<t<t<t<i</</</<t<t<t</<t<h</<h</<b<t<t<t<p<b</</</<t<p<b</</</</<t<t<p<b</</</<t<p<b<b</</</</<t<t<p<b</</</<t<p<b</<b</</</</<t<t<p<b</</</<t<p<b</</</</<t<t<p<b</</</<t<p<b</</</</<t<t<p<b</</</<t<p<b</</</</<t<t<p<b</</</<t<p<b</</</</<t<t<p<b</</</<t<p<b</</</</<t<t<p<b</</</<t<p<b</</</</</</<t</</</</</</<d<s</<s<a</<a</<a</<a</<a</<a</</</</</Connection
closed by foreign host.

I use debian-patched 2.9g (unpacked debian-patched 2.9f and applied diff
manually)

--

-- 
Matus UHLAR - fantomas, uhlar@... ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
Atheism is a non-prophet organization. 

Request Already Recorded message doesn't hammer the point in enough

Actually this isn't clear enough for my English:

  WWWOFFLE Request Already Recorded
  Your request for URL
  http://www...
  has already been recorded for download.

I would say:

  WWWOFFLE Request Previously Recorded
  Your request for URL
  http://www...
  has already been recorded for download.
  So there is no point in you asking this additional time, Holmes 

Or something.

Hmmm, 'previously' might not imply still on the queue though.
Anyway, 'already' for me is the common word companies use to say 'really
in the queue'.

Yes, if one compares the
WWWOFFLE Request Recorded and
WWWOFFLE Request Already Recorded
messages, one will know the difference.
However the latter means the former if one has never encountered the former.

Warning: Failed to get name/IP address for host ... [Name or service not known].

Help. On one of my machines, if one tries to do ANYTHING with wwwoffle,
from the time of boot until first connecting to the Internet, one gets

# wwwoffled -c /etc/wwwoffle/wwwoffle.conf
wwwoffled[3769] Warning: Failed to get name/IP address for host 'jidanni4' [Name or service not known].
wwwoffled[3769] Important: WWWOFFLE Demon Version 2.9f (with ipv6,with zlib,with gnutls) started.
wwwoffled[3769] Information: WWWOFFLE Read Configuration File '/etc/wwwoffle/wwwoffle.conf'.
wwwoffled[3769] Information: Running with uid=13, gid=13.
wwwoffled[3769] Information: Read in 0 trusted certificates.
wwwoffled[3769] Important: Detached from terminal and changed pid to 3772.
# wwwoffle -online -c /etc/wwwoffle/wwwoffle.conf
wwwoffle[3775] Warning: Failed to get name/IP address for host 'jidanni4' [Name or service not known].
wwwoffle[3775] Warning: Unknown host '0.0.0.0' for server [Address family for hostname not supported].
wwwoffle[3775] Fatal: Cannot open connection to wwwoffle server 0.0.0.0 port 8081.
# hostname
jidanni4
# host `hostname`
jidanni4 has address 127.0.0.1

After connecting to the Internet all works normally.

The problem occurs no matter what one puts in wwwoffle.conf, no matter
what one does with /etc/hosts, no matter what one does with pdnsd. Help.

Stopping an ongoing "wwwoffle -fetch" action?

request URL, but not if already in cache

Consider the following situation (running WWWOFFLE 2.9a under Linux):

Suppose I have a list of URLs, say, URL1 URL2 URL3..., some of which
are already present in the cache.  Now I want to make sure that, once
I am online again, those and only those URLi will be fetched that are
not already in the cache.

- One way to do this would be to start the browser and request each
  one of the URLi, which would do the right thing (show those pages
  that are already in the cache, mark for fetching those that are
  missing) but is extremely tedious if there are many URLs.

- The simplest I have come up with is

    cat <list-of-URLs> | xargs -i wwwoffle -o '{}' > /dev/null

  , which seems to work.

But what I would really like is some additional option such that

    cat <list-of-URLs> | xargs wwwoffle -<new-option>

will do the right thing, i.e., `wwwoffle -<new-option> URL1 URL2...`
would behave like `wwwoffle URL1 URL2...` for URLi not already cached
but skips those that are not present (and outputs some message like
'URLi is already in the cache, will not be fetched again' on stderr).

Would this be a valuable feature to add?  And is there any chance this
will actually be added in the future?  Comments?

Best regards, and many thanks to Andrew for WWWOFFLE which has been in
constant use here for many years -

Albert.

"WWWOFFLE - Will Get" not exactly HTTP 404

Looking at RFC 2616, I was thinking HTTP 404 "WWWOFFLE - Will Get" is
not really the same as HTTP 404 "Not Found", which some browsers (e.g.,
emacs-w3m) treat as real bad.

Therefore, wwwoffle.conf should perhaps allow one to tamper with (all)
the (different) HTTP Status Codes WWWOFFLE returns, as one might want to
pick e.g., for "WWWOFFLE - Will Get", one of
202 Accepted
306 (Unused)
408 Request Timeout
409 Conflict
504 Gateway Timeout
or maybe that is all just asking for more trouble.

add-cache-info vs. multipart/x-mixed-replace

Why doesn't add-cache-info get added here
when viewed in Firefox? Well it's some kind of
http://en.wikipedia.org/wiki/Server_push#HTTP_server_push technology,
$ set https://bugzilla.wikimedia.org/buglist.cgi?quicksearch=jidanni
$ firefox $@; wwwoffle-read $@
Content-Type: multipart/x-mixed-replace;boundary="------- =_aaaaaaaaaa0"

WARNING: YOUR BROWSER DOESN'T SUPPORT THIS SERVER-PUSH TECHNOLOGY...
$ wwwoffle $@; wwwoffle-read $@
Content-Type: text/html; charset=UTF-8 ...

So apparently in the first instance wwwoffle is not ready to deal with
multipart. Maybe it should put add-cache-info content into each of the
html parts?

wwwoffle -offline; wwwoffle -online

Now that I have unlimited 64/256K ADSL and thus browse lots more
(Geritol club pages), I notice myself doing
$ wwwoffle -offline; wwwoffle -online
once or twice a day, lest the Lasttime index become unwieldy.
Sure I know how to filter things out of the index, but I still wanted to
keep you other users aware of what we've spotted here at the Gorilla
behaviour self observation lab. Not that I'm seeking a cure or anything.

Re: Bad cert ident jidanni2.jidanni.org from jidanni2: accept? (y or n)

Andrew took the trouble of writing this long answer, and though the
problem hasn't reoccurred, I thought I'd post it to the mailing list in
case it might help someone one day.

amb@... (Andrew M. Bishop) writes:

> Hi,
>
>> Hello. It was a ho-hum day here offline with emacs-w3m.
>> The only interesting things is that it asked me
>> Bad cert ident jidanni2.jidanni.org from jidanni2: accept? (y or n)
>>
>> But that is localhost, and I bend over backwards,
>> LocalHost
>> {
>>  <?php print php_uname(n)."\n";?>
>>  <?php print php_uname(n).".jidanni.org\n";?>
>>  localhost
>>  127.0.0.1
>>  ::ffff:127.0.0.1
>>  ip6-localhost
>>  ::1
>> }
>> in the script I use to create wwwoffle.conf
>>
>> Maybe wwwoffle should create a certificate or something for localhost.
>
> There should be a certificate for localhost.  You will get this if you
> connect to http://localhost:8443/ or http://127.0.0.1:8443/.
>
> The problem is that jidanni2.jidanni.org and jidanni2 are the same
> machine but it isn't possible for them to share a certificate.  We
> need to provide the certificate *before* the client will send us the
> HTTP request that contains the hostname that it is connecting.  This
> means that the best we can do is to ask the operating system what the
> hostname of the server socket is.
>
> This is a more general problem on the internet; it isn't WWWOFFLE
> specific.  While it is possible for many DNS names to point to the
> same IP address and share a web server it isn't possible to share an
> HTTPS server.  A unique IP address is needed for each DNS name.
>
> Your options are:
>
> 1) remove jidanni2 from LocalHost (but then you won't be able to
>    connect using that name and HTTP).
>
> 2) Always use the fully qualified hostname when playing with HTTPS.
>
> 3) Use localhost rather than a hostname (if it is the same machine).