World: r3wp
[!Cheyenne] Discussions about the Cheyenne Web Server
older newer | first last |
Dockimbel 27-Sep-2008 [2821x4] | 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. | |
TomBon 29-Sep-2008 [2825] | hi doc, where can I find the syntax for the alias modul? (I wan't create a directory - cgi - alias) |
Dockimbel 29-Sep-2008 [2826] | ALIAS /url-path %filename (%filename can't be a directory) |
TomBon 29-Sep-2008 [2827] | thx doc, but what if I want to access cgi's in a directory 'outside' the document root? |
Dockimbel 29-Sep-2008 [2828x3] | 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 | |
TomBon 29-Sep-2008 [2831] | thx for the info |
Dockimbel 29-Sep-2008 [2832] | Btw, why bother with CGI scripts when you can use RSP script which are far more powerful ? |
Graham 30-Sep-2008 [2833x2] | 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. | |
Terry 30-Sep-2008 [2835] | Anyone got Vista working? |
Graham 30-Sep-2008 [2836x3] | huh? |
are you saying that you have seen this problem? | |
If that is the case, it must be the windows calls | |
Dockimbel 30-Sep-2008 [2839] | 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 ? |
Graham 30-Sep-2008 [2840x4] | 32 bit |
I see instances of Rebol start up, and the port 80 is opened. | |
but no response | |
3 instances | |
Henrik 30-Sep-2008 [2844] | I wonder if Vista shuts off ports below 1024 for non-administrator users? |
Graham 30-Sep-2008 [2845x2] | I added rebcmd to the firewall exceptions |
ok, where does one change the port ? | |
Henrik 30-Sep-2008 [2847] | It may not have something to do with the firewall. Linux does this even without firewalls. |
Graham 30-Sep-2008 [2848] | listen [ 80 ] |
Henrik 30-Sep-2008 [2849] | in httpd.cfg |
Graham 30-Sep-2008 [2850x2] | Yes, works on 8080 |
interesting. | |
Henrik 30-Sep-2008 [2852] | Then they have probably adopted that feature. Nice to know. |
Graham 30-Sep-2008 [2853] | 1024 is good too. |
Henrik 30-Sep-2008 [2854] | What about 1023? :-) |
Graham 30-Sep-2008 [2855x4] | let me test 81 |
Hmm. Index appears on 81 but scripts don't work. | |
ok, 1024 scripts don't work either | |
just the home page appears | |
Henrik 30-Sep-2008 [2859] | But scripts work on 8080? Are you testing on the local machine or via network? |
Graham 30-Sep-2008 [2860x7] | localhost |
yes, scripts work on 8080 | |
A question about post/put Here's my little test file <html><title> RSP PUT test </title> <%= request/posted %> </html> | |
When I do this with the modified http protocol page: read/custom http://localhost:8080/put.rsp [ PUT %rebview.exe ] I get this <html><title> RSP PUT test </title> file=%/D/che19/Cheyenne/incoming/zmmnfoto.tmp </html> | |
but there is nothing in the incoming directory. | |
So, how do I access the file I sent with my PUT ? | |
I'm not at all clear on how to support a REST call Say, I have something like this POST /@api/deki/pages/=patients%252F300/contents HTTP/1.0 how would i process that so the correct rsp page deals with the request? | |
Dockimbel 30-Sep-2008 [2867x2] | PUT file : the tmp file is deleted once the HTTP response is sent back to client. If you want to keep the file, you need to either rename it (with its original name) or move it elsewhere. |
It's a security feature to avoid saturating server's disk with unwanted files. | |
Graham 30-Sep-2008 [2869x2] | Ok, got it. |
And my REST question? | |
older newer | first last |