World: r3wp

Just thinking that if you need to create signed headers eg. for Amazon 
requests, then these functions should be readily accessible rather 
than tucked inside a scheme somewhere

Just had another thought, if the headers already contain a content-length, 
then make-http-request should not set it again ...

This would be where you are PUT ing a binary file and you already 
know the length, so you set it in the spec ...

All the stuff is defined in the http module - it's the only part 
if the internals that has been put in a module, so far.

Clarification: The http server mode is meant to be good enough for 
Doc to build an R3 Cheyenne on. If he feels the need to bypass it 
and go down to the tcp level, that would be a failure.

so would I access make-http-request ?

I can't say right now - ask me again tomorrow.

what I need is a function that traverses all the objects to find 
a function ....

Going out :)

running away from me??  Happens a lot :(

It's just a fling - I'll be back :)

my candle will still be burning ...

For instance, in writing the AWS stuff, Maarten basically had to 
write his own http scheme ... because it wasn't easy to reuse the 
existing stuff.

I hope we can avoid that need for r3

if you look at the port object! after eg. opening rebol.com, there 
is a port/scheme/actor object, and then the actor object seems to 
be duplicated in port/actor ...

Is there actually any documentation on using the http apart from 
read ?

http://www.rebol.net/docs/HTTPScheme state diagram.png

Just a question about eg.

open http://www.rebol.com


Does 'open take the url, turn it into a port object, and then invokes 
the http scheme'' open on the port object?

scheme's 'open on the port object?

actually what is the question ? :-)

it's doing what you noted, so what ?

just a stream of consciousness like Marcel Proust

:-)

So, if you write your own schemes ... open must invoke the correct 
'open some how

looks like 'open is a native ... no source given

you're seeking the proto-open ?

still streaming ..

AFAIK there's virtually no R3 documentation

i think you know this source system/intrinsic/make-port

ahh.. that helps

there's no trace/net ?

I guess it's download wireshark time :(

HEAD / HTTP/1.0
Accept: */*
Accept-Charset: utf-8
Host: www.rebol.com
User-Agent: REBOL

HTTP/1.1 200 OK
Date: Wed, 06 Jan 2010 07:28:08 GMT

Server: Apache/1.3.37 (Unix) mod_auth_passthrough/1.8 mod_log_bytes/1.2 
mod_bwlimited/1.4 PHP/4.4.7 FrontPage/5.0.2.2635.SR1.2 mod_ssl/2.8.28 
OpenSSL/0.9.7a
Last-Modified: Fri, 01 Jan 2010 21:19:01 GMT
ETag: "3f44376-2667-4b3e66c5"
Accept-Ranges: bytes
Content-Type: text/html
Via: 1.1 bc1
Content-Length: 9831
Connection: close

this was from ...


r: read open [ scheme: 'http host: "www.rebol.com" method: 'head 
port-id: 80 ]

but probe r
[x/ 9831 none ]

well I guess it tells me something is there .. as I don't get an 
error.  But 9831 is not very useful content.

r: read open [ scheme: 'http host: "www.rebol.com" method: 'head 
port-id: 80 headers: [ User-Agent: "Graham" Content-length: 0 ]]
works to override the headers

read p: open [scheme: 'http host: "www.rebol.com" method: 'head port-id: 
80 ]
probe p/state/info/headers
gives more information without wireshark

That's useful ... I thought I molded the whole p and didn't see anything 
...

must initiate the path var to get a response from the server:
read [ scheme: 'http path: host: "www.rebol.com" method: 'head]

** Access error: protocol error: "Server error: HTTP/1.1 400 Bad 
Request"

ok, to send stuff ... need to set a content: in the port spec.

[ content: "ehlo" scheme: 'http ..etc ]

You're sending 

HEAD www.rebol.com HTTP/1.0
Accept: */*
Accept-Charset: utf-8
Host: www.rebol.com
User-Agent: REBOL

which is invalid

ah ok

Ok, we seem to have some basic information now on how to use the 
http protocol :)

This is a little inconsistent .. if I read www.rebol.com I get a 
binary returned

If I read http://www.compkarori.co.nz:8090 I get a string returned 
instead

in the latter case, there's no port/state/info ...

Infact port/state is none

looks like the port structure is being clobbered

anyway the state object is set to none in the latter case ...

I wonder why that should be ...

Gabriele: why is port/state set to none in the latter http read?