From: "Mathieu" <lejatorn@gmail.com>
To: 9fans@9fans.net
Subject: [9fans] alternative port with webfs?
Date: Mon, 16 Mar 2009 00:18:23 +0100 [thread overview]
Message-ID: <055fe646e2d88c0e525db62af670caa3@smgl.fr.eu.org> (raw)
Hi all,
I'm working on something that will use http requests so I figured using
webfs instead of reinventing the wheel might be a good idea, even though
I've been hinted on #plan9 that it's far from perfect.
My first try was to duplicate some code from /sys/src/cmd/webfs/webget.c
and it seemed that I couldn't get a reply from a server
listening on a port other than 80, using that syntax for the url:
http://host:port/path. Then I tried the same thing with webfsget
and I also got a 'Connection refused'.
I've just had a quick peak in /sys/src/cmd/webfs/url.c and looking at
the comments it seems that this kind of syntax for the url should be
directly supported when writing it to webfs. Haven't looked yet at the
code though.
So am I missing something, or is it just not implemented yet?
Cheers,
Mathieu
next reply other threads:[~2009-03-15 23:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-15 23:18 Mathieu [this message]
2009-03-16 0:40 ` Gorka Guardiola
2009-03-16 1:23 ` Mathieu
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=055fe646e2d88c0e525db62af670caa3@smgl.fr.eu.org \
--to=lejatorn@gmail.com \
--cc=9fans@9fans.net \
/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 NNTP newsgroup(s).