World: r3wp

If you need the HTTP client for Uniserve, just let me know, I have 
a much more recent unreleased version that should work better than 
the old one in Uniserve 0.9.9.

sure ..

I guess that the HTTP method and URI query parameters are not related.

what I read is that parameters are supposed to be sent as custom 
headers with PUT

but I guess that's harder to process

from RSP, you just have to look in request/headers to get custom 
headers.

what do you mean the REST URLs have to point to a rsp resource?

with REST you don't have a static page to point to

for now, if you want that your requests be processed by Cheyenne, 
you have to.

Async HTTP client for UniServe: http://softinnov.org/tmp/HTTP-client.zip

T'hanks.

HTTP.r shoud go in UniServe/protocols/, libs/ should go in UniServe/

Need to go now...

ok, thanks ..

what version of core does cheyenne need?
Will it run on some core 2.5?

I was playing around with core on Win CE and 2.5 I believe is that 
last update...

Cheyenne needs at least 2.7.5. It should work on 2.5 I guess if you 
backport some mezzanines (like EXTRACT) and emulate some natives 
(like UNLESS). You also need CALL or LAUNCH in order to support RSP 
and CGI scripts.

Cheyenne 0.9.19 Preview Release : http://cheyenne-server.org/tmp/cheyenne-r0919.zip

This release hasn't been much tested, that's what I've called it 
PR. I'll make the official release in a few days.

Main changes are :
- an improved PHP support (now works reliably)
- sandboxed RSP webapps (as much as it's possible in R2)
- now compatible with REBOL 2.7.6
- bugfixes

See ChangeLog.txt file in the archive for complete description.

Watch out for regressions in your RSP webapps that might be caused 
by the new RSP sandboxing system. For those having a server in production, 
test your RSP applications carefully before upgrading.

hi doc, where can I find the syntax for the alias modul? (I wan't 
create a directory - cgi - alias)

ALIAS /url-path %filename (%filename can't be a directory)

thx doc, but what if I want to access cgi's in a directory 'outside' 
the document root?

Cheyenne serves content only from the document root.

But nothing stops you to use wrapper CGI to execute REBOL code outside 
of the document root (using do %...) if it's really required.

to use => from using

thx for the info

Btw, why bother with CGI scripts when you can use RSP script which 
are far more powerful ?

Anyone got the lastest distro working?  Mine just hangs on do %cheyenne.r

very odd ...must be something to do with Vista ... the cheyenne.exe 
works fine on XP, but does nothing for me on Vista.

Anyone got Vista working?

huh?

are you saying that you have seen this problem?

If that is the case, it must be the windows calls

I don't have Vista installed, so can't test. I guess that's probably 
an issue with one of the win32 API functions used by Cheyenne on 
startup. Did you tested on Vista 32-bit or Vista 64-bit ?

32 bit

I see instances of Rebol start up, and the port 80 is opened.

but no response

3 instances

I wonder if Vista shuts off ports below 1024 for non-administrator 
users?

I added rebcmd to the firewall exceptions

ok, where does one change the port ?

It may not have something to do with the firewall. Linux does this 
even without firewalls.

listen [ 80 ]

in httpd.cfg

Yes, works on 8080

interesting.

Then they have probably adopted that feature. Nice to know.

1024 is good too.

What about 1023? :-)