Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
General
GeneralPortable MacsHardwareNetworking
Applications
Mac ApplicationsEudoraFirefox / MozillaInternet ExplorerOutlook ExpressMS OfficeEntourageExcelPowerPointWordVirtual PCMedia PlayerOther MS Products
Programming
Mac ProgrammingCodeWarriorPerl
Country Specific
Australian Mac GroupUK Mac Group

Mac Forum / Applications / Mac Applications / July 2008



Tip: Looking for answers? Try searching our database.

iCab and caches and home server

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
dorayme - 21 Jun 2008 09:07 GMT
Running a home server I have noticed that iCab (but not Safari) fails to
load recent changes to linked CSS files. I have the prefs set rationally
and as recommended by iCab "Load files from best source" which depends
on the server notifying the browser that there has been an update. The
server (that comes with OS X) obviously does the job well for HTML files
because, for example, inline CSS instructions are immediately
implemented.

Not quite sure if this is an iCab bottleneck or a server one, is there
some config setting for the home server to tell browsers that hey, the
css file has changed. Beyond my pay grade to know which or how to
improve situation.

I know I can set iCab to always get from the web rather than cache, that
is a fix but with some downside as you will appreciate.

Signature

dorayme

Alexander Clauss - 21 Jun 2008 11:55 GMT
> Running a home server I have noticed that iCab (but not Safari) fails to
> load recent changes to linked CSS files. I have the prefs set rationally

In case you're using MacOSX 10.5.x, then this issue is caused by a bug
of "Leopard". Deleting the Web Cache of iCab should fix this problem for
a while.

Signature

Alexander

dorayme - 21 Jun 2008 13:08 GMT
> > Running a home server I have noticed that iCab (but not Safari) fails to
> > load recent changes to linked CSS files. I have the prefs set rationally
>
> In case you're using MacOSX 10.5.x, then this issue is caused by a bug
> of "Leopard". Deleting the Web Cache of iCab should fix this problem for
> a while.

No, I have been using Tiger 10.4.10

You know, Alexander, this is a problem I think I have had for a very
long time with iCab, from many versions back. It is not the end of the
world but I am curious as to why Safari detects it so quickly but not
iCab. I will make some further tests with other browsers.

I have no idea how Safari always seems to know the css has been changed.

Be nice if one could set prefs to cache images only? They are the big
hog.

Signature

dorayme

Sander Tekelenburg - 21 Jun 2008 14:20 GMT
In article
<doraymeRidThis-22CC44.22084521062008@news-vip.optusnet.com.au>,

> > > Running a home server I have noticed that iCab (but not Safari) fails to
> > > load recent changes to linked CSS files. I have the prefs set rationally
[quoted text clipped - 7 lines]
> You know, Alexander, this is a problem I think I have had for a very
> long time with iCab, from many versions back.

Confirmed [Mac OS X 10.4.11]. This was introduced in iCab 4. The only
way to get it to see that the server's external CSS file is newer than
the cached one is to Shift-click the reload button (Cmd-Shift-R still
does nothing). There's some evidence that this is not a network issue,
as getting iCab 4 to apply certain settings changes, like en/disabling
javascript or plugins or adding/changing filters, also requires a
Shift-click on the Reload button.

For general browsing this might not be a big issue, but when you're
developing a site it can get quite annoying. Perhaps it would help if
these cache options would be available through the Filter Manager, so
you can use a different cache settings for sites you're developing. (I
rely on the Filter Manager to ensure that my user CSS is disabled on
sites I develop, for instance).

[...]

> I have no idea how Safari always seems to know the css has been changed.

Safari provides far fewer configuration options. It probably simply
behaves more like iCab's "always load files from the web" cache option.

Signature

Sander Tekelenburg, <http://www.euronet.nl/~tekelenb/>

Mac user: "Macs only have 40 viruses, tops!"
PC user: "SEE! Not even the virus writers support Macs!"

dorayme - 24 Jun 2008 12:21 GMT
> In article
> <doraymeRidThis-22CC44.22084521062008@news-vip.optusnet.com.au>,
[quoted text clipped - 32 lines]
> Safari provides far fewer configuration options. It probably simply
> behaves more like iCab's "always load files from the web" cache option.

Thanks for this info, if it arises again I will try your keystroke
suggestions. For some reason, now I return to this issue, I cannot
reproduce the trouble! When viewing a site on my home server, changing
some heading CSS <h1>...</h2> in a linked CSS sheet was immediate on
reload, iCab set for load files from 'best source' and use caches ticked.

Signature

dorayme

Sander Tekelenburg - 09 Jul 2008 16:34 GMT
> In article
> <doraymeRidThis-22CC44.22084521062008@news-vip.optusnet.com.au>,

[... prefs->Caches: "always load from 'best' source" enabled]

> > > > Running a home server I have noticed that iCab (but not Safari) fails to
> > > > load recent changes to linked CSS files. I have the prefs set rationally

[...]

> Confirmed [Mac OS X 10.4.11]. This was introduced in iCab 4. The only
> way to get it to see that the server's external CSS file is newer than
> the cached one is to Shift-click the reload button (Cmd-Shift-R still
> does nothing).

I think I may have found the problem. Cmd-r (and its equivalent
Navigate->Reload) does not load the changed CSS file. But the Reload
button does. (No Shift key required at all. My mistake.)

Still looks like a bug to me. The Reload button should not behave
different from Cmd-R.

> There's some evidence that this is not a network issue,
> as getting iCab 4 to apply certain settings changes, like en/disabling
> javascript or plugins or adding/changing filters, also requires a
> Shift-click on the Reload button.

Same thing here. Getting iCab to apply a toggle of
javascript/plug-ins/the Filter Manager (and perhaps other settings)
requires clicking the Toolbar's Reload button. Cmd-r reloads but does  
not apply the changed settings.

Alexander, dorayme, can you reproduce this?

Signature

Sander Tekelenburg, <http://www.euronet.nl/~tekelenb/>

Mac user: "Macs only have 40 viruses, tops!"
PC user: "SEE! Not even the virus writers support Macs!"

dorayme - 09 Jul 2008 23:36 GMT
> I think I may have found the problem. Cmd-r (and its equivalent
> Navigate->Reload) does not load the changed CSS file. But the Reload
> button does. (No Shift key required at all. My mistake.)
>
> Still looks like a bug to me. The Reload button should not behave
> different from Cmd-R.

I'm afraid I can't confirm this at the moment, both command R and reload
button update the changes I made to a linked css file on my machine
immediately using either home server or direct 'finder to browser'.

Looks like it is more complicated.

Signature

dorayme

Sander Tekelenburg - 11 Jul 2008 04:34 GMT
In article
<doraymeRidThis-9C0C94.08360510072008@news-vip.optusnet.com.au>,

[...]

> > Cmd-r (and its equivalent
> > Navigate->Reload) does not load the changed CSS file. But the Reload
> > button does. [...]
>
> I'm afraid I can't confirm this at the moment

Alexander found the bug, in WebKit apparently, and fixed it in iCab. (I
imagine it'll be available in the next public version.)

> , both command R and reload
> button update the changes I made to a linked css file on my machine
> immediately using either home server or direct 'finder to browser'.
>
> Looks like it is more complicated.

It turned out the bug only shows when the web page has focus (as opposed
to for instance the Toolbar). Otherwise it behaves as it should.
Probably that explains your findings. (If not, it must be even more
complicated... :))

Signature

Sander Tekelenburg, <http://www.euronet.nl/~tekelenb/>

Mac user: "Macs only have 40 viruses, tops!"
PC user: "SEE! Not even the virus writers support Macs!"

dorayme - 11 Jul 2008 07:27 GMT
> In article
> <doraymeRidThis-9C0C94.08360510072008@news-vip.optusnet.com.au>,
[quoted text clipped - 20 lines]
> Probably that explains your findings. (If not, it must be even more
> complicated... :))

Thanks for looking into this. And Alexander too, of course. As you say,
the benefit should appear in next update.

Signature

dorayme

 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.