[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Lynx-dev] back to the question on lynx vs wiki
|
From: |
Virden, Larry W. |
|
Subject: |
[Lynx-dev] back to the question on lynx vs wiki |
|
Date: |
Fri, 18 May 2007 07:36:50 -0400 (EDT) |
As you may remember, I reports a strange interaction I am experiencing
on http://wiki.tcl.tk/ . Here's the latest info on the situation.
If anyone has any suggestions, we'd love to hear them.
----
Hi Larry,
Thanks for your persistence in helping me track down this bug.
Virden, Larry W. wrote:
> one of the things I have never noticed before today is that when going
> to edit a page, I see lynx display
> HTTP/1.1 200 OK
> for a number of seconds before being able to continue, then after
> submitting an update for a page, lynx displays
> HTTP/1.1 302 OK
> and after a search, it displays
> HTTP/1.1 200 OK
> for a number of seconds before continuing.
>
> I don't recall seeing these before today.
>
Here's what I did: I got one of your session headers, verbatim, from the wiki
logs. I turned it into this sequence of bytes:
'GET /11 HTTP/1.0
Host: wiki.tcl.tk
Accept: text/html, text/plain, text/css, text/sgml, */*;q=0.01
Accept-Encoding: gzip, compress, bzip2
Accept-Language: en
User-Agent: Lynx/2.8.7dev.4 libwww-FM/2.14 SSL-MM/1.4.1 OpenSSL/0.9.6
>From: address@hidden
Referer: http://wiki.tcl.tk/12101
Cookie2: $Version="1"
Cookie: wikit=lvirden
'
And the wiki returned me this:
'HTTP/1.1 200 OK
Date: Thu, 17 May 2007 22:57:38 GMT
Server: Wub 2.0
etag: "tid0x4a801bb0.1179442658461135"
cache-control: public, max-age=0, must-revalidate
content-length: 7416
content-type: text/html; charset=utf-8
last-modified: Tue, 15 May 2007 20:47:00 GMT
Connection: close
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html
lang='en'> <head> <title>Wiki</title>
<meta name='robots' content='noindex,nofollow' />
<style type='text/css' media='all'>@import url(/wikit.css);</style>
</head>
<body>
...
'
(here presented with most of the body elided to save space.)
So: I can tell from this that Wub accepts your connection, processes
the header, and returns something to your lynx.
>From which I deduce that what it's returning is offensive to lynx, in
some way.
I can imagine some kinds of offense lynx might take: (1) perhaps end
of line convention is offensive - I discount this, as we've had happy
relations with lynx at some point, (2) the character encoding offends
lynx - this is possible, I don't know much at all about character
encodings, (3) the fact that Wub is blatting back a series of HTTP/1.1
fields at Lynx might offend it.
I think there are three /1.1 fields in the cited conversation: etag,
cache-control, Connection.
Do you think one of your Lynx contacts could cast an eye over this and
give some opinion about what might be causing Lynx problems? I'm sure
that if it's a back-compatibility problem, then the problem is stemming
from my lack of adherence to standards, but I don't know which part of
rfc2616 I'm failing. I'd certainly like to keep /1.0 browsers happy,
or at least semi-functional, for as long as they exist.
Colin.
--
Tcl - The glue of a new generation. <URL: http://wiki.tcl.tk/ >
Larry W. Virden <mailto:address@hidden><URL: http://www.purl.org/NET/lvirden/ >
Even if explicitly stated to the contrary, nothing in this posting should
be construed as representing my employer's opinions.
-><-
- [Lynx-dev] back to the question on lynx vs wiki,
Virden, Larry W. <=