World: r3wp

I got it working with that sample pem .. the stupid mistake is that 
if you uncomment it like this 
; [https]
accept  = 443
connect = 80
TIMEOUTclose = 0

instead of like this 

[https]
accept  = 443
connect = 80
TIMEOUTclose = 0


you get some strange errors ... now I need to make those bought certs 
work somehow 

( I WILL WRITE A TUTORIAL ABOUT THIS .. how to setup cheyenne with 
stunnel)

where did my last message go?

(messages are here after restart .. sorry)

I compared the modulus and public exponent of key and cert and they 
are the same, but I saw another thing.. related to "half length" 
of the key that worked.

When stunnel starts it says "Wrote 1024 new random bytes to /root/.rnd" 
.. the certs are 2048 bit .. do you think this the problem could 
be that stunnel expects the 1024 byte cert/key ? (the sample cert/key 
taht worked was 1024 byte)

I use apache2-MPM as a reverse proxy in front of Cheyenne for the 
same reasons (static serving, ssl), works flawlessly, but now is 
time to move to nginx. Looking at MacPorts variants for nginx, there 
are many options that I see interestings:
root/trunk/build alpha% port variants nginx
nginx has the variants:
	dav: Add WebDAV support to server
	flv: Add FLV (Flash Video) streaming support to server
	mail: Add IMAP4/POP3 mail proxy support

 ssl: Add SSL (HTTPS) support to the server, and also to the mail 
 proxy if that is enabled
	status: Add /nginx_status support to the server

 perl5: Add perl support to the server directly within nginx and call 
 perl via SSI
	realip: Using nginx as a backend
	addition: Append text to pages
	substitution: Replace text in pages

 gzip_static: Avoids compressing the same file each time it is requested

 google_perftools: Enable Google Performance Tools profiling for workers

 upload: Enable Valery Kholodkov's upload module (http://grid.net.ru/nginx/upload.en.html)
	universal: Build for multiple architectures

I will try intalling nginx too now... I was trying this with stunnel 
for 3 hours and google all I could think of without much luck.. I 
learned a lot more about certs, that is good

Probably it's soemthign about how I create the pem .. maybe I didn't 
position them right (baceuse I see nothing related to 1024 2048 that 
I suspected)

some benchmarks http://blog.mudy.info/tag/nginx/interesting performances! 
8)

Tryed stunnel once, had stability issues, but that may have been 
me or OSX implementation..

Wel I am afraid it won't be so easy with nginx either.. I need to 
take a break , I will try again in the evening.. if anyone succesfully 
setup chained ssl certs with stunnel .. any hint is more than welcome

I got the nginx running with my cert ... I got the same error as 
stunnel , but then I found that my cert must be first and other in 
chan are later .. reverse to some examples on net and to stunnel 
examples (maybe there is the same thing?)

now I need to make it reverse proxy to cebelca

Yay it works !!!

screenshot of latest version of cebelca btw: http://www.refaktor.si/blog/img/cebelca.biz.norm.png

I wrote a how to on setting up stunnel with cheyenne a couple of 
years ago ... it was easy.  Now i just have to find where I published 
it!

Could be useful to have on the cheyenne site.

Graham .. did you have multiple certificates (root intermediatte 
and yours) ?

nginx rules!

no.

SVN revision 12: Response/redirect default code changed to 302 (issuing 
a 303 could cause unwanted effect on HEAD requests). /TEMP option 
replaced by /STRICT for sending back code 303. RSP API documentation 
updated accordingly.

I use lighttpd and reverse proxy to Cheyenne. Works great.

Has anyone created a RSP site where every page can be edited via 
the browser?  I think rebol.com is like that ...

SVN r13, minor fixes :

 o RSP: fix for scripts not returning any data (test.rsp: <% 1 %>)	

 o RSP: words in sandbox context renamed to lower the risk of collision 
 with user script words.

Maybe a rebol-to-json function couldl be included into Cheyenne  
...

If we can get one that works!

:-)

working on it  ;-)

yess... done !

JSON built in Cheyenne: (replying in javascript channel)

I thought I'd just mention it here... a it's a bit odd, and perhaps 
not entirely reproducible.  But I got my JS calendar working.  But 
I could not see any data coming in from my rsp script that was pulling 
data from the db and sending it back as json until I put some debugging 
statements in .. and then it works.  Bizarre.  Or some browser cache 
issue.

Just using a few ?? to log to the trace.log file so it wouldn't even 
be seen by the calling script ...

You can test if it's a browser cache issue by requesting the script 
using the READ function from REBOL console. Can you make a small 
standalone RSP script that  shows this issue?

heh ..  I don't think 'read evaluates JS :)

the docs say you can set the timeout to whatever in the webapp httpd.cfg 
but when I set it to 2:00:00, it still times out well before that.

Where's the curecode for Cheyenne?

Not back online yet.

This works for me :
	webapp [
		virtual-root "/testapp"
		root-dir %www/testapp/
		auth "/testapp/login.rsp" 
		timeout 02:00:00
	]

ahhh.... mea culpa

I used timeout: 02:00:00  .. ie a set word

that should rise an error when starting with -v

SVN r15

FEAT: scheduler lib added
FEAT: 'job config keyword added (CRON-like jobs)

FIX: cheyenne freezing on exiting (only if config reloading was used)

Warning: the scheduler integration with Cheyenne is at beta stage, 
minimaly tested, so if you want to put it in production, take the 
time to test it well.

I've noted in my todo list to extend the RSP API to be able to add/delete 
jobs (for now, the list is static, loaded from config file and cannot 
be accessed from RSP).

FEAT ??

Do you mean "Done ?

FEAT[URE]

yes, means done

Doc - does Cheyenne already enable setting handlers for particular 
filetypes? I mean - equivalence to:

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


For Cheyenne only users, it is not important, they can use RSP, but 
for those who want to have chance to migrate between Apache and Cheyenne 
in CGI mode, it might be usefull. I expect it not being a priority 
for you though ...

But the scheduler is still very fresh, no logging, not much tested,...

Need to check the sources, I don't remember how far we are now.