[9fans] telnet to port (and webfs debug)

[9fans] telnet to port (and webfs debug)

[Giacomo Tesio]

Hi, I'm having an hard time to debug a problem with http clients in
plan9/qemu (actually 9front, but I guess my questions apply to all
plan9 versions).

DNS and ping works properly, just http fails.

I suspect it's a proxy issue. I have set httpproxy environment
variable but with no success: both hget and mothra doesn't works.

I can connect to the qemu host webserver on port 80 and receive the
proper page, but for any other address I can't obtain a response.

The proxy does not log any access.

Now, to debug this issue, I'd like to telnet the proxy port and
manually forge an http request.

However I can't understand hot to specify a port reading man telnet.

What's plan9 equivalent of

   telnet www.google.com 80



Giacomo

Re: [9fans] telnet to port (and webfs debug)

[lucio]

>    telnet www.google.com 80

telnet tcp!www.google.com!80

some bits are optional.  Check dial(2).

Lucio.

Re: [9fans] telnet to port (and webfs debug)

[Quintile]

I have s feeling that get is a script that accesses webfs, and maybe the 9front mothers does the same. are you running webfs?

-Steve





> On 12 Feb 2015, at 11:02, Giacomo Tesio <giacomo@tesio.it> wrote:
> 
> Hi, I'm having an hard time to debug a problem with http clients in
> plan9/qemu (actually 9front, but I guess my questions apply to all
> plan9 versions).
> 
> DNS and ping works properly, just http fails.
> 
> I suspect it's a proxy issue. I have set httpproxy environment
> variable but with no success: both hget and mothra doesn't works.
> 
> I can connect to the qemu host webserver on port 80 and receive the
> proper page, but for any other address I can't obtain a response.
> 
> The proxy does not log any access.
> 
> Now, to debug this issue, I'd like to telnet the proxy port and
> manually forge an http request.
> 
> However I can't understand hot to specify a port reading man telnet.
> 
> What's plan9 equivalent of
> 
>   telnet www.google.com 80
> 
> 
> 
> Giacomo

Re: [9fans] telnet to port (and webfs debug)

[Giacomo Tesio]

[-- Attachment #1: Type: text/plain, Size: 1218 bytes --]

Yes hget is an rc script running on webfs.

Giacomo
Il 12/Feb/2015 13:14 "Quintile" <steve@quintile.net> ha scritto:

> I have s feeling that get is a script that accesses webfs, and maybe the
> 9front mothers does the same. are you running webfs?
>
> -Steve
>
>
>
>
>
> > On 12 Feb 2015, at 11:02, Giacomo Tesio <giacomo@tesio.it> wrote:
> >
> > Hi, I'm having an hard time to debug a problem with http clients in
> > plan9/qemu (actually 9front, but I guess my questions apply to all
> > plan9 versions).
> >
> > DNS and ping works properly, just http fails.
> >
> > I suspect it's a proxy issue. I have set httpproxy environment
> > variable but with no success: both hget and mothra doesn't works.
> >
> > I can connect to the qemu host webserver on port 80 and receive the
> > proper page, but for any other address I can't obtain a response.
> >
> > The proxy does not log any access.
> >
> > Now, to debug this issue, I'd like to telnet the proxy port and
> > manually forge an http request.
> >
> > However I can't understand hot to specify a port reading man telnet.
> >
> > What's plan9 equivalent of
> >
> >   telnet www.google.com 80
> >
> >
> >
> > Giacomo
>
>

[-- Attachment #2: Type: text/html, Size: 1758 bytes --]

Re: [9fans] telnet to port (and webfs debug)

[cinap_lenrek]

the httpproxy variable is read by webfs on startup only. webfs is usually
started in your $home/lib/profile to provide http client service.

just setting httpproxy before running hget or mothra has no
effect on the proxy setting unless you start a new webfs instance.

so try:

httpproxy=http://proxy:port
webfs
hget http://www.google.com/

when that works, set the httpproxy variable at the top of your
$home/lib/profile before webfs is started to make it permanent.

--
cinap

Re: [9fans] telnet to port (and webfs debug)

[Giacomo Tesio]

I did already tried this, but without success, but I tried it again
just to be sure, still without success.

I tried to telnet the proxy with telnet tcp!host!port and it worked as
expected ("GET http://www.google.com" printed its bloated html).

This limit the issue boundaries to webfs (since, as far as I can see,
hget is "just" a wrapper of it), since both squid and the tcp stack
proved to work properly.


The problem is, I can't figure out how to debug webfs. Any tip?

Note that it worked once, a few days ago, when I managed to sysupdate
(setting http_proxy.host in /usr/glenda/.hgrc).



Giacomo



2015-02-12 17:27 GMT+01:00  <cinap_lenrek@felloff.net>:
> the httpproxy variable is read by webfs on startup only. webfs is usually
> started in your $home/lib/profile to provide http client service.
>
> just setting httpproxy before running hget or mothra has no
> effect on the proxy setting unless you start a new webfs instance.
>
> so try:
>
> httpproxy=http://proxy:port
> webfs
> hget http://www.google.com/
>
> when that works, set the httpproxy variable at the top of your
> $home/lib/profile before webfs is started to make it permanent.
>
> --
> cinap
>

Re: [9fans] telnet to port (and webfs debug)

[cinap_lenrek]

heres how it should look like (tuttle.9hal:8888 is my proxy servr):

term% httpproxy=http://tuttle.9hal:8888 webfs -d; hget http://google.com
clientctl: url http://google.com
http(0): GET http://google.com/
hdial [1] tcp!tuttle.9hal!8888
-> GET http://google.com/ HTTP/1.1
Host: google.com
User-Agent: Mozilla/5.0 (compatible; hjdicks)
Connection: keep-alive
Referer: http://google.com/
Accept: */*

<- HTTP/1.1 302 Found

--
cinap

Re: [9fans] telnet to port (and webfs debug)

[Giacomo Tesio]

Ok fixed. The problem was plain stupid: I did not prepended "http://"
to httpproxy, setting it to just proxy:port.

However, I noted that webfs -d option is not documented. Nor is the
need to prepend http:// to httpproxy (I suppose however that this
could be taken as default).
Whenever I'll find my way to acme and plan9 I'll send you a patch...


Thanks you all for your help!


Giacomo


2015-02-13 10:11 GMT+01:00  <cinap_lenrek@felloff.net>:
> heres how it should look like (tuttle.9hal:8888 is my proxy servr):
>
> term% httpproxy=http://tuttle.9hal:8888 webfs -d; hget http://google.com
> clientctl: url http://google.com
> http(0): GET http://google.com/
> hdial [1] tcp!tuttle.9hal!8888
> -> GET http://google.com/ HTTP/1.1
> Host: google.com
> User-Agent: Mozilla/5.0 (compatible; hjdicks)
> Connection: keep-alive
> Referer: http://google.com/
> Accept: */*
>
> <- HTTP/1.1 302 Found
>
> --
> cinap
>

Re: [9fans] telnet to port (and webfs debug)

[erik quanstrom]

> User-Agent: Mozilla/5.0 (compatible; hjdicks)

does anybody remember what the hardware that inspired this was?
and why proper marshalling code couldn't be written.  c structures
can't really be trusted with memory layout.

- erik

Re: [9fans] telnet to port (and webfs debug)

[Charles Forsyth]

[-- Attachment #1: Type: text/plain, Size: 401 bytes --]

On 13 February 2015 at 14:13, erik quanstrom <quanstro@quanstro.net> wrote:

> does anybody remember what the hardware that inspired this was?
> and why proper marshalling code couldn't be written.
>

It wasn't hardware: it was a large package of existing protocol code that
needed to run
but made too many assumptions about structure and structure member
alignments,
prompting the pragma.

[-- Attachment #2: Type: text/html, Size: 812 bytes --]

Re: [9fans] telnet to port (and webfs debug))

[erik quanstrom]

> No webfs required!
>
> There's a factotum extension I wrote a while back that is bundled with
> Mercurial version 2.2+:  http://mercurial.selenic.com/wiki/FactotumExtension.
> If you're using the mercurial contrib package from either jas or myself, it
> should be enabled by default.

thanks to both you and jas for the work on hg.

- erik

Re: [9fans] telnet to port (and webfs debug))

[Steven Stallion]

[-- Attachment #1: Type: text/plain, Size: 470 bytes --]

On Fri, Feb 13, 2015 at 5:30 AM, Giacomo Tesio <giacomo@tesio.it> wrote:
>
> Note that, strangely enough, hg ignores the .hgrc in your home directory.
> The hgrc(8) speak about Unix (and Windows) but since GNU is Not U...
> ehm... Plan9 is not Unix (:-D), I can't say where to write it.
>

Hi Giacomo,

This might explain some of what you are seeing:
http://mercurial.selenic.com/wiki/Plan9FromBellLabs

Your hgrc should be placed under $home/lib.

Steve

[-- Attachment #2: Type: text/html, Size: 970 bytes --]

Re: [9fans] telnet to port (and webfs debug))

[Steven Stallion]

[-- Attachment #1: Type: text/plain, Size: 400 bytes --]

On Fri, Feb 13, 2015 at 5:59 AM, <cinap_lenrek@felloff.net> wrote:

> yes, patch would be welcome :-)
>

No webfs required!

There's a factotum extension I wrote a while back that is bundled with
Mercurial version 2.2+:  http://mercurial.selenic.com/wiki/FactotumExtension.
If you're using the mercurial contrib package from either jas or myself, it
should be enabled by default.

Steve

[-- Attachment #2: Type: text/html, Size: 892 bytes --]

Re: [9fans] telnet to port (and webfs debug))

[cinap_lenrek]

yes, patch would be welcome :-)

--
cinap

Re: [9fans] telnet to port (and webfs debug))

[cinap_lenrek]

hg is using ape port of python which comes with its own http library.
wrote a hg extentsion that makes it use webfs instead, so i can
keep my credentials in factotum/secstore:

[extensions]
hgwebfs=

in your $home/lib/hgrc

--
cinap

Re: [9fans] telnet to port (and webfs debug))

[Giacomo Tesio]

For future reference: hg (and thus sysupdate) simply ignores
$httpproxy variable, it honors $http_proxy instead.
Thus if you are using plan9 behind a proxy you need to set

term% httpproxy=http://proxy.hostname:port # (don't forget "http://"!)
term% http_proxy=proxy.hostname:port

Once it works, you can add it at the beginning of your lib/profile.


Note that, strangely enough, hg ignores the .hgrc in your home directory.
The hgrc(8) speak about Unix (and Windows) but since GNU is Not U...
ehm... Plan9 is not Unix (:-D), I can't say where to write it.


Giacomo

2015-02-13 10:59 GMT+01:00 Giacomo Tesio <giacomo@tesio.it>:
> Ok fixed. The problem was plain stupid: I did not prepended "http://"
> to httpproxy, setting it to just proxy:port.
>
> However, I noted that webfs -d option is not documented. Nor is the
> need to prepend http:// to httpproxy (I suppose however that this
> could be taken as default).
> Whenever I'll find my way to acme and plan9 I'll send you a patch...
>
>
> Thanks you all for your help!
>
>
> Giacomo
>
>
> 2015-02-13 10:11 GMT+01:00  <cinap_lenrek@felloff.net>:
>> heres how it should look like (tuttle.9hal:8888 is my proxy servr):
>>
>> term% httpproxy=http://tuttle.9hal:8888 webfs -d; hget http://google.com
>> clientctl: url http://google.com
>> http(0): GET http://google.com/
>> hdial [1] tcp!tuttle.9hal!8888
>> -> GET http://google.com/ HTTP/1.1
>> Host: google.com
>> User-Agent: Mozilla/5.0 (compatible; hjdicks)
>> Connection: keep-alive
>> Referer: http://google.com/
>> Accept: */*
>>
>> <- HTTP/1.1 302 Found
>>
>> --
>> cinap
>>