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
Marshal Linfoot wrote:
LiteSpeed has a log with optional debug output but it's mostly server
state information (ie. processes starting/stopping). I couldn't find
anything useful.
I discovered a nifty FF add-on called Live HTTP Headers, though.
Here's what it shows for the production site using the old-fashioned
way of including css and for the test site using sns. The only
differences I can spot are the addition of the "Etag" and
"If-None-Match" headers in the test site responses. Is this
significant?
The html files returned are the same except for the <link ... /> tags.
http://octopusgardenyoga.com/
GET / HTTP/1.1
Host: octopusgardenyoga.com
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9)
Gecko/2008061015 Firefox/3.0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 300
Connection: keep-alive
Cookie: __utma=64320817.730990810.1201637965.1201870961.1202442307.5;
__utmz=64320817.1201870961.4.2.utmcsr=octopusgardenyoga.com|utmccn=(referral)|utmcmd=referral|utmcct=%2Flists%2Fadmin%2F;
style=Default; _session_id=a398654d739c03309b141883e3ae8f6c
If-Modified-Since: Wed, 23 Jul 2008 16:08:48 GMT
HTTP/1.x 200 OK
Content-Type: text/html; charset=utf-8
Last-Modified: Fri, 25 Jul 2008 03:05:45 GMT
Content-Encoding: gzip
Vary: Accept-Encoding
Transfer-Encoding: chunked
Date: Fri, 25 Jul 2008 03:05:45 GMT
Server: LiteSpeed
Connection: Keep-Alive
Keep-Alive: timeout=5, max=100
----------------------------------------------------------
http://octopusgardenyoga.com/styles/elastic.css
GET /styles/elastic.css HTTP/1.1
Host: octopusgardenyoga.com
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9)
Gecko/2008061015 Firefox/3.0
Accept: text/css,*/*;q=0.1
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 300
Connection: keep-alive
Referer: http://octopusgardenyoga.com/
Cookie: __utma=64320817.730990810.1201637965.1201870961.1202442307.5;
__utmz=64320817.1201870961.4.2.utmcsr=octopusgardenyoga.com|utmccn=(referral)|utmcmd=referral|utmcct=%2Flists%2Fadmin%2F;
style=Default; _session_id=a398654d739c03309b141883e3ae8f6c
If-Modified-Since: Wed, 23 Jul 2008 16:51:31 GMT
HTTP/1.x 200 OK
Content-Type: text/css; charset=utf-8
Last-Modified: Fri, 25 Jul 2008 03:05:45 GMT
Content-Encoding: gzip
Vary: Accept-Encoding
Transfer-Encoding: chunked
Date: Fri, 25 Jul 2008 03:05:45 GMT
Server: LiteSpeed
Connection: Keep-Alive
Keep-Alive: timeout=5, max=100
----------------------------------------------------------
http://test.octopusgardenyoga.com/
GET / HTTP/1.1
Host: test.octopusgardenyoga.com
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9)
Gecko/2008061015 Firefox/3.0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 300
Connection: keep-alive
Cookie: __utma=64320817.730990810.1201637965.1201870961.1202442307.5;
__utmz=64320817.1201870961.4.2.utmcsr=octopusgardenyoga.com|utmccn=(referral)|utmcmd=referral|utmcct=%2Flists%2Fadmin%2F;
_radiant_session=34d224ec40d533ed1ac0fc36474823de
If-Modified-Since: Fri, 25 Jul 2008 02:24:00 GMT
If-None-Match: "465d8f78af243db4736e38c4452ee778"
HTTP/1.x 304 Not Modified
Content-Type: text/html; charset=utf-8
Last-Modified: Fri, 25 Jul 2008 03:01:58 GMT
X-Runtime: 0.20425
Etag: "465d8f78af243db4736e38c4452ee778"
Date: Fri, 25 Jul 2008 03:01:58 GMT
Server: LiteSpeed
Connection: Keep-Alive
Keep-Alive: timeout=5, max=100
----------------------------------------------------------
http://test.octopusgardenyoga.com/css/elastic
GET /css/elastic HTTP/1.1
Host: test.octopusgardenyoga.com
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9)
Gecko/2008061015 Firefox/3.0
Accept: text/css,*/*;q=0.1
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 300
Connection: keep-alive
Referer: http://test.octopusgardenyoga.com/
Cookie: __utma=64320817.730990810.1201637965.1201870961.1202442307.5;
__utmz=64320817.1201870961.4.2.utmcsr=octopusgardenyoga.com|utmccn=(referral)|utmcmd=referral|utmcct=%2Flists%2Fadmin%2F;
_radiant_session=34d224ec40d533ed1ac0fc36474823de
If-Modified-Since: Wed, 23 Jul 2008 16:36:09 GMT
If-None-Match: "f95c66d251410f2f579f72e87fd28049"
HTTP/1.x 304 Not Modified
Content-Type: text/css; charset=utf-8
Last-Modified: Wed, 23 Jul 2008 16:36:09 GMT
X-Runtime: 0.01098
Date: Fri, 25 Jul 2008 03:01:58 GMT
Server: LiteSpeed
Connection: Keep-Alive
Keep-Alive: timeout=5, max=100
----------------------------------------------------------
On Thu, Jul 24, 2008 at 10:43 AM, Chris Parrish
<[EMAIL PROTECTED]> wrote:
Yes, you got it right. But I need some help from other Radiant users out
there.
And, as I mentioned in my other email. This one's serving up with a
"HTTP/1.1 200 OK" response so it looks like SnS could be the culprit. But I
have *no* idea where to look in LiteSpeed to find out why it thinks the
response should be 404 -- I've never used it. Anyone?
Does it have some sort of log or is there a debugging tool?
TextAssetResponseCache must be handing over something different than the
standard ResponseCache that pages use and LiteSpeed is choking on this
difference. But I'm not getting this behavior on my development machine
(which uses mongrel to serve up the content).
-Chris
_______________________________________________
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
