World: r3wp

I think I found the problem in Uniserve:

In uni-engine.r, replacing:

call join form to-local-file system/options/boot [" -s " cmd]

with:

call join form to-local-file system/options/boot [" -sq " cmd]

quiets it down

Thanks for the fix, it will be part of the next release.

great :-)

Doc, are you considering simple HTML templates for .rsp pages, or 
is that already possible?

Such as converting a block of values to a table:

<% print html-table read %. %>

It's not on my Todo list, I plan to make a higher level framework 
for building web applications, where I don't want to mess anymore 
with HTML or Javascript. Kind of VID dialect that compiles to HTML+CSS+JS.

cool

Just like RoR, RSP can use the following <%= %> instead of <% print 
... %>

Kind of VID dialect that compiles to HTML+CSS+JS.
 Now, that's what I'm talking about!!!

Doc - that would be too wonderful, us HTML challenged programmer 
types would be so very happy with such an option!

hi to Gregg -- thx for the invitation to your world...

oops, probably the wrong place ... plz. excuse the noob

http://www.softinnov.org/is not working?

not here either.

umm,  okay, well maybe this is the right place for a small problem 
I've encountered with  cheyenne / uniserve -- maybe not an issue 
with the server but me being new to rebol -- btw this is on windows 
2000 and happens with both cheyenne and uniserve -- when I go to 
any cgi or rsp page a new rebol console pops up in front of the browser! 
Is there anywhere in the uniserve / cheyenne source where I can disable 
this behavior?

Softinnov.org is back online. There's some bad URL requests using 
not supported HTTP method that sometimes crash Cheyenne. I'm working 
on a fix for this and will publish it asap.

Re DerekR: just look above at Henrik's message, it shows the patch 
to hide the REBOL console when CGI or RSP scripts are processed.

Hi Doc / Nenad -- excellent! (Jeez, there's the answer staring me 
in the face at the top of the window!)

;-)

While you're here -- I noticed that Cheyenne failed to fetch a jpg 
image that had spaces in its src url -- e.g. "red rock river.jpg" 
-- and "red rock river.jpg" didn't help either ...

(uniserve didn't have a problem with this btw)

Could you please fill an issue ticket about that in the bugtracker 
please : http://www.softinnov.org:8000/curecode/project.rsp?id=4

Sure thing Doc!

-- btw wanted to say how delighted I was to find a lightweight, scriptable, 
no-hassle-to-install, x-platform web server -- many thanks!!

I plan to make a new release this week, only bugfixes.

Great! --

Thanks! That's exactly why I've built Cheyenne ;-) I plan to improve 
it much more in features, speed, easy configuration,...

I had a problem with port 80 at first -- this both in uniserve and 
cheyenne -- changed the hardcoded port assignment in httpd.r to 8880 
and it worked fine

Are you on Linux or OSX ?

Can the port # be reassigned from the command line

This is on Windows 2000

use : -p 8880

thx!

woops -- just attempted to register a new acct w/ yr bugtracker -- 
got the email confirming, went to the indicated url -- found a bug 
;-) --> > RSP Error Trapped<

Error Code : 	310
Description : 	script error !
validate-user has no refinement called update
Near : 	[if not validate-user/update request/content [err?: yes]]
Where : 	protected-exec

recursive bug-tracking bug ...

can't log-in either --> "Error: Account not yet activated"

funny bug... I guess that's a regression from last restore after 
the server's disk crashed...

almost kafkaesque, that bug ;-)

give me a few minutes to fix that...

anyway i'll try checking back later, see if i can get in -- grazie!

I've reset the server, it should be ok now.

Doc? -- just filled in a ticket but when I tried to submit I got 
"Access Denied" ... bzzzzt

btw also determined that the URL spaces bug also happens w/ anchor 
& location "href" and in the address-bar

but this _doesn't_ happen when running UniServe 0.9.9

good luck with the bug-hunting!!

After rebooting my OSX machine, Cheyenne doesn't work anymore. I 
didn't change anything. It starts and runs and launches its task 
handlers, but there is no access from a webbrowser. Does it create 
some kind of start up log so I can tell what's wrong?

also it seems to launch two instances of itself.

Firewall?  non-persistent changes to ip tables can get ya.

firewall is inactive

you can set the log to verbose

Do you launch Cheyenne with root privileges (for <1024 listen ports) 
? Use this command line to debug : ./cheyenne -vvv