codesite-noreply at google
Sep 8, 2009, 7:28 AM
Views: 839
Permalink
|
|
Issue 568 in cherokee: Optimizing redirects
|
|
Status: Accepted
Owner: alobbs
Labels: Type-Enhancement Priority-Medium OpSys-All Component-Logic
Performance
New issue 568 by ste...@konink.de: Optimizing redirects
http://code.google.com/p/cherokee/issues/detail?id=568
(04:20:11) drobbins: hiya
(04:23:17) drobbins: I think I found a way to optimize cherokee's
handling of redirects, if I am understanding my protocol dump correctly
(04:26:49) drobbins: it looks like cherokee closes the connection when
it returns a 301 to a client
(04:27:12) drobbins: however the client should be able to re-use this
connection, as the redirect may be to a file on the same site
(04:27:38) drobbins: say a user requests /doc/en/funtoo/about, cherokee
will redirect to /doc/en/funtoo/about/ (with trailing slash) and close
the connection.
(04:27:54) drobbins: the client then needs to initiate a new tcp/http
connection to request the redirected file.
(04:28:00) k001operator is weggegaan (quit: Remote closed the connection).
(04:28:13) drobbins: it seems like cherokee's handling of this could be
optimized.
(04:29:40) drobbins: of course I'm an HTTP protocol newbie so I could be
wrong
(05:11:21) Skinkie: drobbins: is this always true?
(05:11:26) Skinkie: also in the keepalive?
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
_______________________________________________
Cherokee-dev mailing list
Cherokee-dev [at] lists
http://lists.octality.com/listinfo/cherokee-dev
|
Issue 568 in cherokee: Optimizing redirects
