r3wp [groups: 83 posts: 189283]
  • Home
  • Script library
  • AltME Archive
  • Mailing list
  • Articles Index
  • Site search
 

World: r3wp

[!Cheyenne] Discussions about the Cheyenne Web Server

Will
15-Dec-2008
[3566]
feature request: add on-global-page-start and on-global-page-end, 
same as on-page-start and on-page-end but executed for all rsp pages, 
not only for webapps
Dockimbel
15-Dec-2008
[3567x2]
Maxim: thanks, it still needs a lot of work to be completed : integration 
of a CureCode instance for bug tracking, writing lot of documentations,...
Will: I'll consider that for the next release.
BrianH
16-Dec-2008
[3569]
Has anyone written Atom or RSS output code in RSP? I am going to 
need to do so right away and every possible speedup helps.
Kaj
16-Dec-2008
[3570x2]
I remember an RSS output snippet. It's probably in the REBOL library
By Chris, if I'm not mistaken
Chris
16-Dec-2008
[3572]
http://www.rebol.org/view-script.r?script=emit-rss.r
Luis
17-Dec-2008
[3573]
http://www.ross-gill.com/page/Atom+in+a+Hurry
BrianH
17-Dec-2008
[3574]
Thank you both :)
Henrik
20-Dec-2008
[3575]
Graham, did you ever get to switch to slicehost or linode?
Maarten
20-Dec-2008
[3576x2]
I have slicehost. Highly recommended.
Fast, super simple. Not the cheapest, but you definetely get what 
you pay for (which is very good, in their case). They also have good 
docs and wikis - that's an example for many services!
Graham
30-Dec-2008
[3578]
What's the minimum you need to run Cheyenne?  the encapped binary 
and what else?
Dockimbel
30-Dec-2008
[3579]
A config file, but if you don't provide one, Cheyenne will create 
a default one in the same folder.
Graham
30-Dec-2008
[3580]
Thanks
Graham
31-Dec-2008
[3581x4]
This is interesting.   I'm launching cheyenne on startup each time 
my app starts.  But to see if it is already running, I check by opening 
a port.
p: open/direct tcp://127.0.0.1:8002 close p


but this causes Cheyenne ( latest encapped version ) to shut down!
I tested this with the above and a rebol console to reproduce it.
I guess I should check with read http://127.0.0.1:8002 instead, but 
that's slower.
but does it mean I can crash any Cheyenne server remotely at will?
Henrik
31-Dec-2008
[3585x3]
Graham, try mine and let's see what happens.
although I still am running an older version...
I have to go for a bit...
Graham
31-Dec-2008
[3588x3]
Oops .. changed this group to non web public ...shouldn't have posted 
this is a web public group
No, it's okay with yours.  I'm guessing it only crashes on localhost.
phew!
Will
31-Dec-2008
[3591]
Graham, do you have any custom services? no problem here with that 
code:
  p: open/direct tcp://127.0.0.1:80 close p  
  p: open/direct tcp://127.0.0.1:80 close p
  p: open/direct tcp://127.0.0.1:80 close p
  p: open/direct tcp://127.0.0.1:80 close p
  p: open/direct tcp://127.0.0.1:80 close p
  read http://127.0.0.1:80                        
;   {<html>
<head>
^-<title>Welcome!</title>
</head>
<body>
<img src="logo.png">
<center>
<h2>Congratulations, you are running Cheye...
Graham
31-Dec-2008
[3592]
this is just the Cheyenne binary ... nothing else, and running on 
8002
Will
31-Dec-2008
[3593]
hmmm, I'm running from source
Graham
31-Dec-2008
[3594x3]
>> p: open/direct tcp://localhost:8002 close p p: open/direct tcp://localhost:8002 
print "ok"
close p
** Access Error: Cannot connect to localhost
** Near: p: open/direct tcp://localhost:8002 print "ok"
>>
the ok does not print because Cheyenne has quit
this though is fine


>> p: open/direct tcp://localhost:8002 print "ok" close p p: open/direct 
tcp://localhost:8002
print "ok" close p
ok
ok

so timing appears critical
Henrik
31-Dec-2008
[3597x2]
Graham, I have to check my console, because I think mine auto-restarts 
on quit.
seems there is nothing in consle
Graham
31-Dec-2008
[3599]
meaning?
Henrik
31-Dec-2008
[3600]
meaning it didn't quit
Graham
31-Dec-2008
[3601x3]
ok
well, reproducible on my system.
I guess we can make this group web-public again.
Will
31-Dec-2008
[3604x4]
keep it non public, there is a wiki on cheyenneserver.org for open 
web
btw Henrik and I are running it on osx
http://cheyenne-server.org/..
maybe someone is attaking you http://ftp.uni-kl.de/25C3/video_h264_720x576/25c3-2909-en-tcp_denial_of_service_vulnerabilities.mp4
8P
BrianH
31-Dec-2008
[3608x2]
Please let us know if there are any security vulnerabilities that 
pop up for Cheyenne, or REBOL network services for that matter.
I am about to use Cheyenne for a project that I have just found out 
will be more public than anticipated.,
Dockimbel
31-Dec-2008
[3610]
Graham: no problem here, testing with 0.9.18 binaries and 0.9.19 
source version, can't reproduce that crash (all tests done on port 
80). WinXP-Pro-SP3 here.
Graham
31-Dec-2008
[3611]
I'm on vista and using port 8002
Dockimbel
31-Dec-2008
[3612x2]
Do the Cheyenne processes disappear when your test fails? If not, 
did you try to access a web page to see if it's still responding?
try => tried
Graham
31-Dec-2008
[3614x2]
I'm watching the task manager ... all 3 cheynne processes quit
I think timing is critical for this bug to appear