Thanks again Chris. I really appreciate all your help with this.

I finally get what you've been saying about the 404 error. If you ask
for the css file directly
( it displays, but the
response header indicates a 404 error. If you ask for it indirectly,
via the <link .../> statement, a 404 status is generated (I assume)
and depending on the browser, the 404 is ignored and the css is
applied (Opera, Safari) or it's not (FF, IE). In any case, the
interesting question is, as you said, "Why is LiteSpeed serving up the
content fine yet assigning a 404 to the page?".

I double checked all the LiteSpeed config settings and don't see
anything unusual. Double checked file permissions/ownerships and all
looks well. Will continue to google around for any clues.

On Fri, Jul 25, 2008 at 9:14 AM, Chris Parrish
> Marshall,  I just saw this message (I use Live HTTP Headers too) as I'm
> preparing to leave on a two day trip.
> So I won't be able to do anything until I get back (didn't want you to think
> I was ignoring you).  The big question still is:
>   Why is LiteSpeed serving up the content fine yet assigning a 404 to
>   the page?
> Again, I'm guessing that it's something with SnS but right now I don't know
> where to start looking.  Any help by the Radiant community here would be
> greatly appreciated.
> If nobody has any suggestions, I'll start analyzing the output of the
> TextAssetResponseCache once I get back to see if I stumble on anything.
>  This one smells weird.
> -Chris

Radiant mailing list

Reply via email to