World: r3wp

If I code a RSP script I know which methods to expect. So, the normal 
pages only use POST, GET. As soon as I create a site that uses other 
methods, I need to make XMLHttpRequest form the client. Than I know 
which methods to handle.

I don't see a problem here.

This is really a blocking point for me at the moment.

If I code a RSP script I know which methods to expect

 Ok, you know but Cheyenne doesn't know unless you told him. So if 
 you don't filter yourself (as you don't want it to be filtered by 
 Cheyenne), you'll most probably return broken pages to client using 
 HTTP methods you didn't expected.

I gave you a solution above to allow any method for your specific 
needs. It shouldn't take you more than 30s to fix it.

Ok, I will try. Even I don't fully undertand what to do.

Should be obvious when you see the code. ;-)

Re HTTPS: there's a ticket opened in RAMBO since October 2006 from 
Maarten asking for that : http://www.rebol.net/cgi-bin/rambo.r?id=4170&
. If Carl could fix it for 2.7.7, that would be a great new feature.

Perhaps it's not easily fixable?

At least Carl should tell us if it can be fixed within a few hours 
of work or needs several days.

What did Carl say when he was asked at the French Rebcon?

IIRC, he said that it was maybe just a flag to set to activate server 
mode, but he had to do some research about it first.

You have tp specifiy a certificate store and a server certificate 
as well. I'd LOVE to have this feature

well a couple of years research hasn't got far.  I wonder who else 
might help Carl enable this?  Is Holger around for a contract job?

I'll be sure to bring it up.

I use Cheyenne as a reverse proxy. I think in this setup the HTTPS 
things is handled by the primary web-server, communication to the 
revers proxy is non encrypted and hence this setup should make it 
possible to use Cheyenne's RSP with HTTPS. Not elegant but it should 
do the job.

yess this is how I have set it up before too... in a test I did with 
apache in front... the appache in revers dns also allows two distribute 
load on several machines, so it also allows to easily scale once 
you've got load.

Yep, that's the idea on it.

And at the moment I use VMs to distribute to other machines. So things 
can move around to different hardware.

DELETE: If I change mod-static/method-support I need to run cheyenne 
from source base. Is the SDK build method / script available as well?

Or should I send you a patch to add additional RSP-reachable methods 
via the httpd.cfg file?

To build a binary from Cheyenne source, just do : enpro (or enface) 
cheyenne.r

You can send me the patch by email.

and correct the include paths!

for your local environment.

SSI:Any examples available?

And, is it possible to "call" a RSP file?

call = include

You can include RSP files .. useful for dynamic headers and footers.

And bodies ;-)

Didn't want to make it confusing for you.

SSI: http://en.wikipedia.org/wiki/Server_Side_Includes

Doc, I'm trying Cheyenne (the encapped version) on a Linux server 
with moderate success. Can I use an httpd.cfg that is not stored 
in the same dir as the Cheyenne executable?

How much of that do you support?

Cheyenne's mod-ssi currently only supports FILE and VIRTUAL directives 
(that's probably 90% of SSI usage). I've planned to add all the other 
missing directives, but it's quite low priority.

Httpd.cfg : no, it has to be in the same folder.

OK, thanks.

Ah wait, maybe not, I need to check the code.

It would be nice to store the exe where it should be and the config 
in /etc.

That's specific to Unix system.

But I already have some specific data folder handling for Windows...so 
why not.

There's a -f %folder/ option for command-line, but it seems to be 
honored only for Windows platforms.

henrik, won't that be a problem if you run more than one chyenne 
instance?

Btw, I always found very user-unfriendly  the Unix approach of dispatching 
application related files through the whole filesystem...Pity that 
the GoboLinux philosophy didn't spread over all the others distros.

Graham, I'm not sure. Would I want to run more than one? I'm not 
counting the processes that Cheyenne manages.

will there still be an option to have it in the same folder if you 
change this? maybe as command line arg

Henrik, you may not want more than one instance running ... but someone 
else might.  so, I think it needs to be as flexible as it can be.

Agree.

Doc, agree too. It's a mess. And a time-killer if you start using 
Linux. Where can I find ABC etc.

I think to add on Unix, search paths for config file in the following 
order : local folder, $HOME, /etc/ . Would that be enough to cover 
all use cases?

fine by me