World: r3wp

Actually, using..  do load %myfile  in my url-to-filename phase.. 
it's loading the functions each time, but I'll move them into main 
boot script when they're stable

only a true geek has fun with this stuff.

( I guess that makes me a geek ;)

So, what are your near future plans for cheyenne?

reach v1.0 ;-)

add all the missing features planned for v1.0 (see the cheyenne's 
web page for more info)

I might be able to help with  this.. 
Customizable HTTP error pages.

What did you have in mind?

RE: "How does Cheyenne's performance and security stack up against 
the other indians (Apache, Cherrokee, Hiawatha, ...)?"


Speed: close to Apache2.x for static files (tested a year ago, so 
new tests need to be conducted).


Security: not chroot-ed and no special protection against ddos attacks 
like Hiawatha, no bandwidth throttling (could be added), no CGI time 
limit (could be added), passes Nikto generic security tests flawlessly 
(last time check : few months ago)

Customizable HTTP error pages: server-side redirection on 4xx and 
5xx errors to any pages, user-defined in config file.

I think a biggy will be SSL support

Have you looked at openSSL ?

Well, I have SSL running in Cheyenne.. it's not pretty, but was quick

I suppose one issue will be connecting to the library.. would require 
view/pro?  Can call the binary, but it's a less elegant solution

Why is it not pretty?

This method is for windows.. and runs a shell

stunnel ?

If you want to try this method for windows.. here's what you do.. 


1) download the windows binary from openssl.. ->   http://www.slproweb.com/products/Win32OpenSSL.html

2) Unzip.. and pull out the openssl.exe file from the bin folder.. 
. drop that file into your cheyenne www folder
3) Create a self-signed cert....
3a) run openssl.exe

3b) enter this line: req -x509 -nodes -days 365 -newkey rsa:1024 
-keyout localhost.pem -out localhost.pem
(localhost is the cert name)

3c) answer the questions... when asked 'who are you?' enter your 
domain,  or 'localhost' as I did 

This will generate the cert in your www folder (this is just a demo... 
the openssl server uses it's location as root www folder)

4) Start up the server... enter this line into openssl:  s_server 
-accept 443 -cert localhost.pem -WWW


Now open any file in your Cheyenne www folder using the https:// 
 protocol

you only need the openssl.exe file for this demo

If you acess Cheynne as https://localhost/myfile.htmlyou won't 
get the second cert warning

Stunnel would work

Wonder what Carl has in mind for library access with R3?

Can always call, but lib access would be nicer.

http://www.compkarori.co.nz:8080/wiki/index.php/HowTos:Stunnel

no go for me

well, I didn't try it ..just documented it!

ok.. working now

So, the howto is correct?

i missed the comment  in front of ;https[] in config

yeah

Works nicely too.. sit in sys tray

don't need to put into root folder (probably not a good place for 
the cert by the way)

and... can use to encrypt other protocols.. bonus

you could use it for cerebus

So, short of making Cheyenne cost $99. by forcing view/pro for lib 
access.. these are probably the best options.

R3 may well have these for free

You'll want to use OpenSSL to generate a cert for Stunnel to replace 
the default

If I have a large amount of html that I want to reuse in each page, 
rather than including it from the disk, can I define them as rebol 
variables to be reduced inside rsp pages?

Like Zope as it were.

And this to save me defining lots of static code in pages that is 
the same everywhere

I guess I can use Max's preprocessor for this

Does the rsp evaluate files included using include-file ?

no

I've converted my site to https as well using the above howto .. 
only took 2 mins.  As you say, I have to generate a new certificate.

https://www.compkarori.co.nz/

Where is the debugging javascript added ?

when debug is true?

I just recently received whole new website for our Xidys site ... 
it is - templates, but there is some php code in there, and it sucks 
- they did not tell me ;-) Unfortunatelly, templates are easy. They 
did a trick, when whole top, bottom section plus left menu is one 
template, and content is "included" into the template, according 
to what item you choose in the menu. The advantage is - you don't 
have repeating part on more than one place. Disadvantage is - when 
you want to display the content part, you easily can't, as that template 
waits for inclusion, does not have headers, and hence it does not 
link to css - that aproach sucks, it does not work without whole 
production environment ....

Terry, what method are you using to intercept 404s?

Chris, I basically set Cheyennes current mod-static to return false 
if 404, then created a module with the same phase with a 'if 404...' 
function. This second url-to-filename is set to 'last' in the new 
module.

Another approach could be to install in your module a callback for 
'filter-output phase (not used in any builtin modules, yet) and test 
the return code. This way, you wouldn't need to patch mod-static 
and if you give it  order: 'first, it should be able to work even 
when I'll add callbacks to that phase. The purpose of this phase 
is to allow last minute changes on the response content, like encoding 
(think about JSON, for example), compressing (gzip, deflate) or encrypting 
it. These kinds of handlers would be installed as 'last in the phase 
callbacks order.

Here's an untested example  :