W3C home > Mailing lists > Public > www-jigsaw@w3.org > March to April 1999

AW: Problem in accessing GIF files

From: Werner Hennrich <weHe@TeleWeb.at>
Date: Mon, 8 Mar 1999 14:01:32 -0500 (EST)
To: "Www-Jigsaw" <www-jigsaw@w3.org>
Message-ID: <001201be6996$0f9eaa60$879f22c3@stuwehe.telekabel.at>

> -----
> Von: www-jigsaw-request@w3.org [mailto:www-jigsaw-request@w3.org]Im
> Auftrag von Christopher William Turner
> Gesendet am: Sonntag, 7. März 1999 05:11
> Cc: Www-Jigsaw
> Betreff: Re: AW: AW: Problem in accessing GIF files
> There is no problem with the Jigsaw server. The problem is an
> incompatibility
> between
> the particular image *files* in the jigsaw release and IE4/Windows.
> Try *not* starting the server and use the "file:" protocol to get
> IE4 to directly
> load the
> image file to prove it.

If I do this, MSIE displays _all_ the images I tried ( /icons ) correct.

I even mounted that /Icons folder in my IIS and could request the gifs
without any problems.

> Therefore there should be no objection to using Jigsaw to serve
> your own sites with
> your
> own images, just don't use any images from the jigsaw release.

So when _without_ JigSaw the images show up propperly you say that is a
proof that the problem is _not_ related to JigSaw ???? I don't understand

OK, I have now put one of my own gifs into JigSaw's Icon folder, lauched
JigSaw and requested http://localhost:8001/Icons/wehe.gif - that worked
fine. Then came the surprise: http://localhost:8001/Icons (an auto-gnerated
index, showing all names and images as well) showed up perfectly, while
http://localhost:8001/Icons/WWW _DID_NOT (showed the names of the gifs but
was unable to display the images). That seems to be a problem with the
indexer on the WWW folder...

I'd say, the objection to using Jigsaw is still up.

Received on Monday, 8 March 1999 14:41:17 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:41:26 UTC