From: Andy Wingo <wingo@pobox.com>
To: Ian Price <ianprice90@googlemail.com>
Cc: guile-devel@gnu.org
Subject: Re: Change to write-request-line
Date: Tue, 06 Dec 2011 20:27:25 +0100 [thread overview]
Message-ID: <87ty5dmrfm.fsf@pobox.com> (raw)
In-Reply-To: <m3sjnfm8tn.fsf@Kagami.home> (Ian Price's message of "Thu, 29 Sep 2011 20:45:24 +0100")
On Thu 29 Sep 2011 21:45, Ian Price <ianprice90@googlemail.com> writes:
> Two patches for the web stuff in guile. The first removes the second
> definition of 'write-uri' from module/web/http.scm. No point having two
> of them after all :-).
Probably better to remove the first one. The second one allocates less,
catches some important error conditions, and doesn't write the fragment
component.
> The second changes 'write-request-line' to write paths rather than full
> uris. Quoth the RFC
>
> The most common form of Request-URI is that used to identify a
> resource on an origin server or gateway. In this case the absolute
> path of the URI MUST be transmitted (see section 3.2.1, abs_path) as
> the Request-URI, and the network location of the URI (authority) MUST
> be transmitted in a Host header field.
>
> While the RFC also says that "The absoluteURI form is REQUIRED when the
> request is being made to a proxy.", reading through the code for Ruby's
> Net::HTTP and Haskell's Network.HTTP, they both seem to just use the
> path and not provide for this situation, so I've held back on including
> a #:absolute-uri? keyword to cover this.
>
> Any thoughts on this?
I guess that's OK. Proxies probably DTRT already, and anyone who wants
something different should be able to write it fairly easily.
One thing though, you are missing the query component. Care to post a
modifed patch?
Thanks, and sorry for the delay!
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2011-12-06 19:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-29 19:45 Change to write-request-line Ian Price
2011-12-06 19:27 ` Andy Wingo [this message]
2012-01-07 0:37 ` Andy Wingo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ty5dmrfm.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=ianprice90@googlemail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).