AltME groups: search

oh, this is web-public, I just read the request of author to not 
publish it publicly yet ... hopefully it is used by the community 
at max ...

And i posted the same request than you

it is now clearer, because of my stack-size request ...

Note that in A87 has a problem with HTTP:

>> read http://www.rebol.net

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


In case you are trying to do something with OSX or Linux, which currently 
only are at A87.

This is not a problem in A88.

its a recurring request since REBOL as firat released.  with R3 we 
will now be able to compile rebol on ANY platform, which allows us.

Gabriele, is it possible to dispatch multiple request to wiki TCP 
examples "pong" server listening on single port? It should be possible 
but for me second request is without response until the first still 
open. Your HTTP scheme is too much complicated to me as lecture reading 
:). I've tried to transform rebol.org webserver to R3, I've got response, 
but seems to me useles to serve one and one only connection at time 
when the port is asynchronous by nature. Any hint?

I think it's because of User-agent in the request

how can i inject request to the socket ?

but with the request injection the reply is the data ....

it's not the only one problem, all the chunks are sent in one massive 
request before the server treat them, i guess

I just added the wish request.

R3 request: Please, please, please... .add a good paranthese balance 
problem report. I don't know how often I have searched for a missing 
[ or ] in either source-code or large data-files. Rebol doesn't give 
a good hint where the problem is.

I think I'll just stick with putting a time stamp on each request 
to foil the cache

so that is the rsp you request that generate the file and upload 
it to google

I'd like to see the response headers of that request , not those 
from requesting the uploaded file

impossible, that is not how it works, cheyenne responds with a redirect, 
that is an answer and has a header, the the browser request the redirected 
url from google server

this is the request


GET /md/creategoogledoc.rsp?gdoc=simple-letter.rtf&patientid=2832&encounter=none 
HTTP/1.1
Host: gchiu.no-ip.biz:8000

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.2) 
Gecko/20090729 Firefox/3.5.2 (.NET CLR 3.5.30729)

Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 300
Connection: keep-alive
Referer: http://gchiu.no-ip.biz:8000/md/Listgoogledocs.rsp
Cookie: RSPSID=QZPTPCZIWWMMYBKWHWRQETGM

I need the response not the request 8)

Robert, how can Cheyenne know that "quantity" must be an integer! 
value if you don't tell it? Cheyenne can't validate that implicitly, 
you have to either use VALIDATE (see API doc) or make your own checking 
routines. By default, all your GET or POST  parameters are treated 
as string! value. If you need to check for their presence or need 
to convert them to another datatype, you have to validate the format 
so that it doesn't error out (or worth, let an hostile request pass).

That first redirection is an authentication request from google so 
it looks like you might not have been logged in to gmail at the time. 
 I used your second suggestion and that seems to work fixing the 
caching issue.  Good work!

Yes, like the one in section "10. Running the server". You need also 
to block direct access on port 80 for your SSL protected resources. 
There are various way to achieve that like using a local firewall 
to block incoming traffic on port 80 from outside (but not from localhost), 
or in per webapp, using a custom 'on-page-start handler testing the 
server port of the incoming request (and rejecting it if port<>443).

What is the best way to make domain.com to www.domain.com redirection 
in Cheyenne .. (seo guy advised me that).. in apache you use mod_rewrite:

RewriteEngine On
RewriteCond %{HTTP_HOST} !^www\.site-assitant\.com$ [NC]

RewriteRule ^.*$ http://www.site-assitant\.com%{REQUEST_URI} [R=301,L]

how I use it: nginx get all the requests, if a file is not found 
it will proxy-reverse the request to cheyenne wich is configured 
with a on-status-code [404 trap.r] . trap.r check the url request 
and either load and respond with an rsp or send a 404

nginx has nice things like you can pre gzip your static content so 
it wont have to compress for each request

attempt [load join request/config/root-dir %/app-init.r] ; TBD: report 
errors !!!

Maybe it's this line in the code that is giving me issues.

Sorry, if I'm rambling a little bit. It's what I'm observing that 
is straight reposted here. Moving a few milimeters forward after 
a whole day's work is a bit frustrating, particularly when it's REBOL. 
:-)


Right now I just see that app-init.r is not run and that the loading 
of it is wrapped in an ATTEMPT in Cheyenne's source, so I basically 
can't see what's going on. From the docs it appears that the app-init.r 
file is required for a web-app, but request/web-app returns a web-app 
name. So am I running a real web-app or what's going on?

Henrik, trying to answer your questions/issues :


to serve multiple document roots on the same site without having 
separate domain names

 => Use sub-domains for such isolation. Everything that's under one 
 domain can be accessed with /.. parent syntax. I think that you can 
 hack it around with ALIAS, custom webapps on-page-start event  handler, 
 but there aren't clean solutions. Use sub-domains for such isolation.

I think webapps require a bit more than static pages?

 => Just to make it clear, webapps are REBOL applications interfaced 
 with external world using RSP scripts. Webapp are not meant to be 
 container for *only* static pages (HTML/CSS/JS/images).


attempt [load join request/config/root-dir %/app-init.r] ; TBD: report 
errors !!! [...] 
RSP: error in events from %app-init.r now logged. 
That's from the change log. That's not correct.

 => Yes it is. What's being logged so far is the errors caught at 
 runtime in event functions declared in app-init. What need to be 
 logged is the LOAD %app-init.r process (syntax errors at boot time).


after a lot of experimentation, the latest encapped version was the 
only one that worked properly.

 Both encap and sources versions works well on Win/Mac/Unix. The issues 
 you have are related to running a rebol app as daemon in console 
 mode on a remote Unix server (without a UI desktop). Cheyenne can 
 work in source mode on such server, but it's much easier and pratical 
 to use it in binary form in such case (typical remote linux server 
 case).

Btw, the usual way to not have to "restart workers" on each app-init 
or other memory cached code is to run cheyenne with -w 0 option (use 
only 1 worker process and kill it after each request) and some verbose 
output for debugging :

 ./cheyenne -vv -w 0 &

21/9-10:52:50.451-[MTA] New request: [[noreply-:-cheyenne-server-:-org] 
[[gchiu-:-compkarori-:-co-:-nz]] %mlxbgiff 11294044 #[none]]

21/9-10:52:50.452-## Error in [uniserve] : On-received call failed 
with error: make object! [
    code: 303
    type: 'script
    id: 'expect-arg
    arg1: 'pick
    arg2: 'series

    arg3: [series! pair! event! money! date! time! object! port! tuple! 
    any-function!]
    near: [pick dns-server random length? dns-server]
    where: 'on-init-port
] !

that query is traversing a lot of layers...some of them might implement 
some sort of retries if first request doesn't work.

What I'm getting however is this


request/content is [file "%/C/Cheyenne/incoming/oixaqcdg.tmp^M^/"]

and the file contains all the post variables and data

I assumed it only put file data there and still captured the non 
file data into request/content

I assumed it only put file data there and still captured the non 
file data into request/content

 => it requires to send data using "multipart/form-data" encoding.

BrianH answered correctly, 'post-mem-limit allows you to set the 
maximum size of incoming data stored in memory. If that threshold 
is reached, all request content data is flushed on disk to avoid 
memory starvation attacks.

When is session created?
 On first request to a webapp resource.

When is session destroyed?

 When you invoke session/end or once the session timeout period has 
 expired and the garbage collector has suppressed it. Not sure what 
 happens if you try to access it after the timeout before GC passing, 
 need to check it.

Session: "On first request to a webapp resource." Hm... I'm not using 
a webapp, just a RSP file. Could this make any problems?

doc, I've got some questions about http.cfg vhost redirection...

www.domain.com:81 [
	redirect 301 "/*" "http://www.domain.net"
]
www.domain.net:81 [
	root-dir %/E/dev/project/my-web/web/www.domain.com
	default %index.rmrk

]


should this work?  cause its not .  I'm still getting a request for 
domain.com and a 404 error.  domain.net works perfectly.   

actually, unless I include a root-dir entry in domain.com config, 
I get an error within cheyenne.

BIND associates a mod handler with one or more file extensions. For 
example:


o bind SSI to [.shtml .shtm] : process those extensions through mod-ssi.

o bind php-fcgi to [.php .php3 .php4] : process those extensions 
thru  mod-fastcgi using a php backend.


The ID value used as first argument of BIND is just a hook used by 
the target mod to know which request it should process (as required 
by config file). See mod-ssi.r as an example.

Additionnaly, from mod functions, you can get your domain or webapp 
config block using req/cfg (you don't have to search in  the whole 
config file which part applies to the request, it's already done 
by Cheyenne).

Max - never mind. If I want to use only Cheyenne, it is not a problem. 
I was thinking around the lines of producing rebol aproach, which 
would be interchangable easily between Apache and Cheyenne, for those 
who can't afford to push their provider to run Cheyenne for them. 
So I thought that following Apache equivalent would be useful. But 
my request surely is not a priority ....

AddHandler rebol-cgi-dispatch .html
Action rebol-cgi-dispatch /cgi-bin/rebol-cgi-dispatch.cgi

can be done easly, source is in your hand , do whatever you want 
with it, sorry I have no time this week and I see no use of timestamps 
in rsp usage, but if I get at least one more same request I will 
add it 8)

hm.. maybe I will need to solve that on nginx level because cheyenne 
will show me localhost as IP for each request

hm... then I would just need to parse url in the script instead of 
using request/content

will the script that get's called see the original url in request/parsed 
or will that be changed too? (I couldn't make it work yet otherwise)

There no exceptions support in Alias. The rewrited url should be 
available in request/headers/location.

Erratum: request/headers/location has nothing to do with aliases.

get the url with this:

url: any [select request/parsed/headers 'internal-referer request/parsed/url]

I'd say one Uniserve handler should normally be able to handle several 
tens of requests per second, so even when you would let each client 
browser do a poll request every second, compared to that you loose 
at least an order of magnitude in scalability with Comet

Comet requires a connection to stay open, so it looks like this will 
take a Uniserve process for each open connection.


A Uniserve process (worker process) is not bound to a given client 
connection. Each worker accepts requests from ANY client connection, 
so it can handle hundreds of Comet-like connections with a few worker 
processes as long as each request doesn't take much time. For example, 
if each request takes 50ms, with 10 worker processes, you can handle 
200 req/sec.

The flag is set when a request is assigned to a process and reset 
when the worker answers back.

This PHP code works fine..

<?php
 
 $password = "ClueCon";
 $port = "8021";
 $host = "127.0.0.1";
 
 function event_socket_create($host, $port, $password) {
     $fp = fsockopen($host, $port, $errno, $errdesc) 
       or die("Connection to $host failed");
     socket_set_blocking($fp,false);
     
     if ($fp) {
         while (!feof($fp)) {
            $buffer = fgets($fp, 1024);
            usleep(100); //allow time for reponse
            if (trim($buffer) == "Content-Type: auth/request") {
               fputs($fp, "auth $password\n\n");
               break;
            }
         }
         return $fp;
     }
     else {
         return false;
     }           
 }
 
 
 function event_socket_request($fp, $cmd) {
    
     if ($fp) {    
         fputs($fp, $cmd."\n\n");    
         usleep(100); //allow time for reponse
         
         $response = "";
         $i = 0;
         $contentlength = 0;
         while (!feof($fp)) {
            $buffer = fgets($fp, 4096);
            if ($contentlength > 0) {
               $response .= $buffer."<br>";
            }
            

            if ($contentlength == 0) { //if contentlenght is already don't process 
            again

                if (strlen(trim($buffer)) > 0) { //run only if buffer has content
                    $temparray = split(":", trim($buffer));
                    if ($temparray[0] == "Content-Length") {
                       $contentlength = trim($temparray[1]);
                    }
                }
            }
            
            usleep(100); //allow time for reponse
            

            //optional because of script timeout //don't let while loop become 
            endless
            if ($i > 10000) { break; } 
            
            if ($contentlength > 0) { //is contentlength set
                //stop reading if all content has been read.
                if (strlen($response) >= $contentlength) {  
                   break;
                }
            }
            $i++;
         }
         
         return $response;
     }
     else {
       echo "no handle";
     }
 }
 
 $fp = event_socket_create($host, $port, $password);
 $cmd = "api show dialplan";
 $response = event_socket_request($fp, $cmd);
 echo $response; 
 fclose($fp);

I can open a port, and get the authentication challenge.. i iget 
a content-type: auth/request.. .when i insert into the port "auth 
Cluecon \n\n" i get no reply.. just times out with a timeout error?

aha, no problem .. how can I read the cookies .. looking at request 
headers I guess (I forgot a little about how exactly cookies are 
doing)

request/headers/cookie

Janko, about the app-init code you've uploaded, just a side note 
: you're loading a *lot* of code (libs?) on each RSP request, this 
is surely slowing down each request a lot. You should be loading 
all these libs in 'on-application-start instead. (btw, "simpauth.r" 
is loaded twice)


About local testing, you can use virtual hosts locally too in Windows 
easily. Just add them to C:\Windows\System32\drivers\etc\hosts file. 
Add them all after 127.0.0.1 (but do not use exactly the same domain 
name as the remote ones or you won't be able to access them anymore). 
I use shortcuts of my real domains for locals : softinnov.org => 
si.org, curecode.org => cc.org, etc...

Janko, about the app-init code you've uploaded, just a side note 
: you're loading a *lot* of code (libs?) on each RSP request, this 
is surely slowing down each request a lot. You should be loading 
all these libs in 'on-application-start instead.

 or you can add them in the httpd.cfg in a worker-libs block, look 
 in Cheyenne/changelog.txt for 'worker-libs'

Janko: "About code loading on on-page-start : yes I know of that, 
I am using it as dev setup so I know latest code is reloaded each 
pageload." 


There's an easier solution for that: add -w 0 argument to Cheyenne's 
command line, this will ensure that the worker process will be reloaded 
for each new request. Here's the command line I use to run Cheyenne 
on my development boxes : C:\Dev\SDK\tools\rebcmdview.exe -s cheyenne.r 
-vv -w 0

Here's a good primer

http://www.indicthreads.com/3625/html-5-websocket-cracks-the-http-request-response-barrier/

SVN r45 : Web Sockets support


FEAT: experimental Web Sockets support added. (See %www/ws.html and 
%www/ws.rsp)
FIX: regression on bad HTTP request filtering. (Thanks to sqlab)
FIX: minor code clean-ups.

Server-side 'connect and 'close sockets events are missing. Not sure 
how easy it will be to add them to the RSP application model. More 
generaly, the web sockets require a shift in the whole application 
model, the RSP engine is tuned to request/response model, not client/server. 
I'm not even sure that such server can be built in a efficient way 
with REBOL without multi-threading support (can't share port! values 
between processes).

No you can't, it won't work (RSP engine use a request/response model), 
but even if you could, that would mean one process per client connection, 
definitely not scalable.

WS.rsp  should look like this

<%

;-- RSP API web sockets specific changes --
;

;   request/web-socket? => true if this is an incoming socket message, 
false if it's HTTP.
;   request/content/data => contains the socket message (string!)

;-- just echo back the message
//prin request/content/data

inc: request/content/data
if inc = "makedrag" [prin "$('#test').draggable();"]  

if inc = "Hello World" [prin "alert('Hello back');"]
 
%>

Not using the default config .. but I get this

26/12-10:17:23.838-[RSP] ##RSP Script Error: 

	URL  = /ws.rsp
	File = www/ws.rsp

	** Script Error : Invalid path value: data 
	** Where: rsp-script 
	** Near:  [prin request/content/data] 


Request  = make object! [

    headers: [Host "localhost:8000" Connection "keep-alive" User-Agent 
    {Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/532.5 
    (KHTML, like Gecko) Chrome/4.0.249.43 Safari/532.5} Accept {application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5} 
    Accept-Encoding "gzip,deflate" Accept-Language "en-GB,en-US;q=0.8,en;q=0.6" 
    Accept-Charset "ISO-8859-1,utf-8;q=0.7,*;q=0.3"]
    status-line: #{474554202F77732E72737020485454502F312E310D0A}
    method: 'GET
    url: "/ws.rsp"
    content: none
    path: "/"
    target: "ws.rsp"
    arg: none
    ext: '.rsp
    version: none
    file: %www/ws.rsp
    script-name: none
    ws?: none
]

the "data" argument can contain anything as long as it's a string! 
value. It will be available on the RSP side in request/content/data.

PHP: quite stable as long as you don't do live %httpd.cfg file reload 
(mess up PHP processes).

do-task in RSP : no, UniServe's model is : one unique dispatcher 
process, one or many worker process.

Timers: no, they require an event loop, worker processes can't have 
one because they are supposed to work in a request/response model.

That comes from the way web socket's connection are initiated, it 
starts like a simple HTTP GET request and the server is supposed 
to validate that request, check access authorization if required, 
etc... So, to avoid duplicating work, I choose to re-use RSP framework 
as much as possible. The initial ws:// URL must point to a valid 
RSP script so that the server can check, for example, RSP session 
cookie for access rights.

aha, I see it now..


btw: I noticed one thing.. when I uploaded file request/conetnt keys 
returned to strings from words .. so I had to do req: request/content 
forskip req 2 [ change req to-word first req ]  to fix them back

I am using 0.9.19, no problem just wanted to mention. 


@Graham: can I ask why are you doing this (checking for file OR data 
in request/content): 
either file? filedata/2 [ 

 write/binary join get-user-dir filename read/binary join incomingdir 
 filedata/2
] [ 
	if filedata/2 [
		write/binary join savedir filename filedata/2
	]
]


I imagine if file is bigger it get's saved and you copy it. But how 
can you then determine the incoming/pwd is this some cheyenne default?

That may be possible, but would be more complicated to support than 
web sockets as the server can't send data without getting a request. 
It will be hard to extend the web socket application framework without 
bloating it. Maybe a separated mod-comet would be a cleaner approach 
(but might duplicate a Iot of code in mod-socket). I will give it 
a look anyway, at least to estimate the time required to support 
it.

Need to try an experiment where a worker thread sends an AJAX request 
to an RSP page, which in turns pushes back via websocket :)

I just found out about a bug I was making and could only be discovered 
when cheyenne was first started, because some word was undefined 
then so it triggered an error, if I did some other things I couldn't 
see it but it would return wrong information in reality .. 


1. is there any way maybe that would make cheyenne "reset" each request 
(for debugging & testing purposes, not production) .. the -w option 
seems not to do this. 


this could probebly be solved by wrapping also those parts in functions 
... another question..


2. Is there any way I could see all globals I created so I could 
find wtich ones I "leaked" unintentionally .. 


it would be very helpfull if rebol could let you define functs that 
would warn you if you used or defined any global words

SVN r61

FEAT: added request/store function to help manage uploaded files 
(see %changelog.txt).
FIX: IE issue with upload.html (cache issue). Works ok in IE now.
DOC: upload API documented in %www/upload.html.

Terry: on-message function => yes, loading a script on each request 
is ok for debugging, but bad pratice for production. I'm not sure 
that WAIT is safe in Cheyenne callbacks, never tested that, this 
function is not supposed to be used in user code inside Cheyenne 
main process (it would work in a RSP script, but will block valuable 
resources and reduce scalability).

Graham,  I've used this code to obtain get/post data in Cheyenne:

REBOL [title: "sitebuilder" file: %sitebuilder.cgi]
print "content-type: text/html^/"
print [<HTML><HEAD><TITLE>"Sitebuilder"</TITLE></HEAD><BODY>]
either system/options/cgi/request-method = "POST" [
    submitted-bin: make string! input
] [
    submitted-bin: system/options/cgi/query-string
]
submitted: decode-cgi submitted-bin

That replaces this Apache CGI code:

#!./rebol276 -cs
REBOL []
print "content-type: text/html^/"
print [<HTML><HEAD><TITLE>"Sitebuilder"</TITLE></HEAD><BODY>]
read-cgi: func [/local data buffer][
    switch system/options/cgi/request-method [
        "POST" [
            data: make string! 1020
            buffer: make string! 16380

            while [positive? read-io system/ports/input buffer 16380][
                append data buffer
                clear buffer
            ]
        ]
        "GET" [data: system/options/cgi/query-string]
    ]
    data
]
submitted: decode-cgi submitted-bin: read-cgi

HTH :)

I thought this scenario could be recreated using WAIT or a loop that 
takes some time. 


Here'a another scenario.. a very typical websocket use..  A request 
comes in from the client "IBM".. the ws-script then checks a remote 
server continuously pushing a new IBM stock quote update, second 
by second forever?

A request comes in from the client 

IBM".. the ws-script then checks a remote server continuously pushing 
a new IBM stock quote update, second by second forever?" 

That's the typical case where you would use set-timer / on-timer.

here is from the change-log:

RSP: new method 'store added to Request object. It simplifies uploaded 
files

   management by abstracting file's location (memory or disk). Example:

			request/store request/content/file %attached/
			

   will save the uploaded file passed as "file" query parameter in %attached/ 
   folder
	  using the original name (!!watch out for security issues!!).
	  
	  		request/store request/content/file %attached/my-file.bin
	  		

   will save the uploaded file with a forced name (original name needs 
   to be saved
	  separatedly if needed).

With the request/store - does it means that the rsp processing starts 
before the upload is finished = stops where the /store is called 
waiting on upload finish?

Ok, so via RSP, I can use request/posted to get the input cotent. 
 That's good.

The "magic" RSP line is:
<% insert tail response/buffer request/posted %>

The server's input request packet times out.

SVN revision 72: File uploading improvements (changes might break 
older scripts)


FEAT: File upload management improved, in-memory uploading removed 
for consistency.

FEAT: request/store specifications changed. Now it renames the temp 
file to its original name by default. Use the new /as refinement 
to move the file (see Changelog).

FEAT: New complete example of file uploading (client and server-side) 
in www/ folder.

FEAT: New config keyword: 'incoming-dir <%/path/> to specify a custom 
incoming folder per domain or per webapp.

Maybe a silly question, but why Carl uses:
  <% insert tail response/buffer request/posted %>
instead of:
  <% print request/posted %>

or just <%=request/posted%> :-)

He's using <% insert tail response/buffer send-chat request/posted 
%>. So the shorter version would be :
<%= send-chat request/posted %>

Can someone give me some guidance on the following I keep getting 
a decoding error.

<%
 	fname: request/content/fname
   	lname: request/content/lname
   	spouse: request/content/spouse
	address: request/content/address
	city: request/content/city
	state: request/content/state
	zip: request/content/zip
	h_phone: request/content/h_phone
	c_phone: request/content/c_phone
	email: request/content/email

 do-sql 'bugs ["INSERT INTO names VALUES (?,?,?,?,?,?,?,?,?,?)"fname 
 lname spouse address city state zip h_phone c_phone email ]
%>

BTW, I normally do it this way

fname: any [ select request/content 'fname copy "" ]

so that the variable is always a string ...

jim: it's also good to use  validate  function before you process 
the request content!

Also the Jim's code does not looks much friendly - too many request/content/ 
paths.

Request parameters are used to transport data from client to server. 
If a parameter is not sent, having 'none seems appropriate. Setting 
them to anything else "by default" will make you loose this important 
information.

Btw, you can easily write (when needed): var: any [request/content/var 
<default value>]

Jim's snippet could be rewritten like that : 
<%
	if none? validate/full [
 		fname	-		*
   		lname	-		*
   		spouse	-		-
		address	-		-
		city		-		*
		state		-		*
		zip		integer!	*
		h_phone	-		*
		c_phone	-		-
		email		email!	*
	][
		req: request/content
		do-sql 'bugs [
			"INSERT INTO names VALUES (?,?,?,?,?,?,?,?,?,?)"
			req/fname
			req/lname
			req/spouse
			req/address
			req/city
			req/state
			req/zip
			req/h_phone
			req/c_phone
			req/email 
		]
	]
%>

I know, but than I can write as Graham var: any [select request/content 
'var <default value>] without validate... At least if the value is 
expected to be a string!.

For the CureCode I have set a new account request in and am getting 
no email. I went back to my Curecode R3 account and requested the 
password email and so far no email.  For new request, status says 
'account not yet activated'

I use something like this in my nginx config:
        location ~ \.(rsp|cgi)$ {
            proxy_pass   http://lucya.desajn.web:8080;
            
            proxy_set_header   X-Real-IP        $remote_addr;

            proxy_set_header   X-Forwarded-For  $proxy_add_x_forwarded_for;
            proxy_set_header   X-URI $request_uri;

            proxy_set_header   if-modified-since $http_if_modified_since;
            
			client_max_body_size       10m;
            client_body_buffer_size    128k;

            proxy_connect_timeout      90;
            proxy_send_timeout         90;
            proxy_read_timeout         90;

            proxy_buffer_size          4k;
            proxy_buffers              4 32k;
            proxy_busy_buffers_size    64k;
            proxy_temp_file_write_size 64k;
        }

What do you mean by that? Cheyenne's UniServe task masters run in 
separate processes, so when one request takes time other task masters 
handle other requests, but within one request your code is executed 
serially, the way you program it. REBOL is single-tasking, after 
all

Terry: enable verbose mode in C starting it with -vvvvv to see if 
C see the request

well the browser needs to request it.  or you need to redirect to 
it.

ah... you can setup all subdomains to use the same root dirs, but 
then the domain name is different in your request object.

I wonder how slow it might be to use a coding style where each page 
is represented by a Rebol object, and to display the page back to 
the browser client, you have a render function that iteractively 
calls the render function of each element of the object.  the object 
initializes by reading the session and request objects when it is 
first instantiated