On Mon, Dec 12, 2011 at 04:38:06PM -0500, Eli Barzilay wrote:
> The common reason to not include it is when the response comes from
> code, and you can't include the size before you've run the code which
> means that you have to hold the complete response somewhere before you
> send it.
Thanks Eli
On Mon, Dec 12, 2011 at 2:32 PM, Jordan Schatz wrote:
> On Mon, Dec 12, 2011 at 11:30:59AM -0700, Jay McCarthy wrote:
> > But the Racket Web server only has request logging by default, not
> response
> > logging, so it makes something up in these positions. I will update the
> > docs to mention t
Eli Barzilay wrote at 12/12/2011 04:38 PM:
...also, in what Jordan posted there was a
Content-Length: 2629
header, so the information is already there.
I think that this part of the format typically represents how much was
*actually* transmitted, not how much was *supposed* to be tran
Three hours ago, Jay McCarthy wrote:
> Alright. I looked into this more.
>
> The 200 and 512 from the log are not about the request, they are about the
> response:
>
> "200 (%>s) [...]"
But the original problem was about the response size...
> But the Racket Web server only has request logging
On Mon, Dec 12, 2011 at 11:30:59AM -0700, Jay McCarthy wrote:
> But the Racket Web server only has request logging by default, not response
> logging, so it makes something up in these positions. I will update the
> docs to mention this.
I think that a single dash is typically used if a value is m
Alright. I looked into this more.
The 200 and 512 from the log are not about the request, they are about the
response:
"200 (%>s)
This is the status code that the server sends back to the client. This
information is very valuable, because it reveals whether the request
resulted in a successful re
> I'll fix it for the next release sometime tomorrow.
Thanks Jay : )
On Fri, Dec 09, 2011 at 06:42:04PM -0700, Jay McCarthy wrote:
> Hah. I just looked at the code and it has always had 200 and 512 hard-coded
> in the logging function. Hah. I'll fix it for the next release sometime
> tomorrow.
>
Hah. I just looked at the code and it has always had 200 and 512 hard-coded
in the logging function. Hah. I'll fix it for the next release sometime
tomorrow.
Jay
On Fri, Dec 9, 2011 at 5:07 PM, Jordan Schatz wrote:
> I have a web server with logging setup like so:
> (serve/servlet start
>
I have a web server with logging setup like so:
(serve/servlet start
#:log-file "../logs/server"
#:log-format 'apache-default)
Here are the headers from a client request
HTTP/1.1 200 OK
Date: Fri, 09 Dec 2011 21:23:16 GMT
Last-Modified: Thu, 08 Dec 2011 05:04:56 GMT
S
9 matches
Mail list logo
