Re: bug in 8.5.6 http package? or maybe tls?
- From: Alan Grunwald <alan.via.aioe@xxxxxxxxxxxxxxxxxxxx>
- Date: Sun, 16 May 2010 20:09:07 +0100
Bryan,
I'm seeing buggy behavior with tcl 8.5.6, tls and http.
The short version is, if I use https rather than http to do a GET
request, the body of the data is coming back as part of the meta data.
If I use http, the data comes back fine. Is this a known bug with
either tls or the http package?
When I use https, the body of the response is empty and the meta data
looks like this:
% parray meta
meta(Cache-Control) = no-cache
meta(Connection) = close
meta(Content-Type) = text/html; charset=utf-8
meta(Date) = Sun, 16 May 2010 15:19:16 GMT
meta(Expires) = Fri, 01 Jan 1990 00:00:00 GMT
meta(Server) = Google Frontend
meta([{"deleted") = false, "modify": "2010-05-14 19:34:39.488957",
"key": "..."}, {"deleted": false, "modify": "2010-05-02
22:12:38.943439", "key": "..."}, {"deleted": false, "modify":
"2010-05-02 00:36:03.472073", "key": "..."}]
Has anyone seen this before? Interestingly, if I include "-validate 1"
to the request, the meta data is well-formed. It's only when the data
is fetched that it gets added to the page metadata.
That sounds very much like a bug that I saw a couple of months ago. Turns out this was reported on bug 2624536, which I think has details of a fix. What version of the http package are you using? I saw it on 2.7.2 .
HTH
--
Alan
.
- Follow-Ups:
- Re: bug in 8.5.6 http package? or maybe tls?
- From: Bryan Oakley
- Re: bug in 8.5.6 http package? or maybe tls?
- References:
- bug in 8.5.6 http package? or maybe tls?
- From: Bryan Oakley
- bug in 8.5.6 http package? or maybe tls?
- Prev by Date: bug in 8.5.6 http package? or maybe tls?
- Next by Date: Re: 'clock microseconds' broken on Windows
- Previous by thread: bug in 8.5.6 http package? or maybe tls?
- Next by thread: Re: bug in 8.5.6 http package? or maybe tls?
- Index(es):
Relevant Pages
|