From: Andrei Borzenkov <arvidjaar@gmail.com>
To: Alan Perry <aperry@snowmoose.com>
Cc: grub-devel@gnu.org
Subject: Re: HTTP with other ports
Date: Wed, 19 Nov 2014 21:22:54 +0300 [thread overview]
Message-ID: <20141119212254.28eea889@opensuse.site> (raw)
In-Reply-To: <546CD2E4.60305@snowmoose.com>
В Wed, 19 Nov 2014 09:27:00 -0800
Alan Perry <aperry@snowmoose.com> пишет:
> On 11/19/14, 9:09 AM, Andrei Borzenkov wrote:
> > В Wed, 19 Nov 2014 08:54:24 -0800
> > Alan Perry <aperry@snowmoose.com> пишет:
> >
> >> Has anyone come up with a general way to change the port number in the http module? Right now it is hard coded to be 80, but it is very common to do HTTP over another port number.
> >>
> >> I was thinking about extending the device name syntax for network devices
> > Does protocol,server:port conflict with anything? (http,server:1234)/foo
>
> I separated the server from the port with a comma
Do you have implementation? Then send a patch for review.
> because that is how
> the protocol is separated from server. I don't think either syntax
> conflicts with anything else,
Actually ':' does conflict with IPv6.
> but I haven't been working with enough
> different parts of GRUB2 to really know.
>
> In my previous note, I mentioned a command for setting the default
> server, but I was really talking about the net_default_server env
> variable. Thinking about it, an alternate default port doesn't make
> sense because you really need to know its protocol as well. Maybe a
> default protocol or protocol/port env variable that includes both allows
> the alternate port for the protocol to be specified?
>
Does not
set root=protocol,server,[?port]
do exactly that?
> alan
>
> >
> >> and/or adding a 'default port' (with a command to set it) to go with
> > default server. I did an implementation that works for my needs but
> > don't think it is a good general purpose implementation.
> >> Has anyone else done work here or have ideas for using alternate port numbers with HTTP?
> >>
> >> alan
> >>
> >>
> >> _______________________________________________
> >> Grub-devel mailing list
> >> Grub-devel@gnu.org
> >> https://lists.gnu.org/mailman/listinfo/grub-devel
> >
> > _______________________________________________
> > Grub-devel mailing list
> > Grub-devel@gnu.org
> > https://lists.gnu.org/mailman/listinfo/grub-devel
>
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/grub-devel
next prev parent reply other threads:[~2014-11-19 18:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-19 16:54 HTTP with other ports Alan Perry
2014-11-19 17:09 ` Andrei Borzenkov
2014-11-19 17:27 ` Alan Perry
2014-11-19 18:22 ` Andrei Borzenkov [this message]
2014-11-19 21:23 ` Alan Perry
2014-11-20 3:36 ` Andrei Borzenkov
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=20141119212254.28eea889@opensuse.site \
--to=arvidjaar@gmail.com \
--cc=aperry@snowmoose.com \
--cc=grub-devel@gnu.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.