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

Gabriele
27-Jun-2007
[1821]
oldes, it is legal but NOT part of query args UNLESS percent-encoded. 
special characters in uris must always be percent-encoded when not 
used as separators.
Graham
27-Jun-2007
[1822x4]
Good question .. yes, it works remotely without ssl.
Cheyenne is running on port 8100, and SSL is directed to that from 
stunnel.
So, if you try 


page: read/custom https://www.compkarori.co.nz/show.cgireduce [ 
'post join "content=" content ]  
then this fails if content is a few kbs

but if you do 


page: read/custom http://www.compkarori.co.nz:8100/show.cgi reduce 
[ 'post join "content=" content ]

it works fine.
What a shame.
Dockimbel
27-Jun-2007
[1826]
So it seems that the issue is either with the HTTPS protocol in REBOL 
or with stunnel.
Graham
27-Jun-2007
[1827x3]
I guess so
So, I need to mock up a webpage to do the same post
and check it out in a browser
Dockimbel
27-Jun-2007
[1830]
Exactly.
Graham
27-Jun-2007
[1831x2]
Hmm.
I don't have a https server I can test ...
Dockimbel
27-Jun-2007
[1833]
Be sure to use the latest Cheyenne beta (0.9.15). It fixes a regression 
bug on multipart data decoding.
Graham
27-Jun-2007
[1834x3]
Do you have a log of which files are changed?
Or do I have to update every file?
I guess I'd better download curl and use that to test with
Dockimbel
27-Jun-2007
[1837]
Sorry, no diff file list. You can update just the files having a 
more recent timestamp.
Graham
27-Jun-2007
[1838x6]
Ok
curl seems to work
curl -k -F upload=@test.ps -F press=OK https://www.compkarori.co.nz/show.cgi
So, I guess this means it's a Rebol https problem :(
Wasn't Gabriele asking for people to test a new http(s) protocol 
??
Does anyone wish to independently confirm my findings with https?
Graham
28-Jun-2007
[1844x4]
Rebol []

data: copy/part read %test.ps 1024
content: copy data
for i 1 100 1 [
	cnt: i * 1024

 page: read/custom https://www.compkarori.co.nz/cgi-bin/measure.rsp
 reduce  [ 'post join "content=" content ]
	parse page [ thru <data> copy received to </data> ]
	either found? received [
		received: to integer! trim received 
		either received = cnt [
			print [ "OK at " cnt ]
			append content data
		][
			print [ "oops .. failed at " cnt ]
			break
		]
	][
		print "failed to read ... "
		halt
	]
]
http continues okay.
https fails at 15360 bytes
and measure.rsp is ..

<html>
<body>

<%
	either content: select request/content 'content [
		print [ <data> length? content </data> ]
	][
		%> Nothing was sent! <%
	]
%>
</body>
</html>
narrowed it down further ..16376 is okay, 16377 bytes fails
Pekr
28-Jun-2007
[1848]
hehe, how can I simulate virtual-host on localhost? :-)
Dockimbel
29-Jun-2007
[1849]
locally define your DNS names in your hosts file (/etc/hosts or C:\WINDOWS\system32\drivers\etc\hosts) 
to be able to simulate locally virtual-hosts.
Graham
29-Jun-2007
[1850]
Doing some more testing... not even sure http is okay.
Pekr
29-Jun-2007
[1851]
ah, thanks!
Graham
30-Jun-2007
[1852x2]
Does the current version of Cheyenne encap?  I tried and I get a 
windows exception when I run the encapped version.
Using 2.6.2.  Downloaded 2.7.5 and same result.
Dockimbel
2-Jul-2007
[1854]
Encmd crashes if 'title keyword is used in 'encap header. It works 
correctly with enpro and enface. So just remove from encap header 
: title "Cheyenne" and it will work.
Graham
3-Jul-2007
[1855]
Thanks .. and that is so strange!
Pekr
5-Jul-2007
[1856]
trying to run php ... how should I configure my fastcgi section properly?

	extern fastcgi [
		command	 "php -b $port"
		pool 	 min 1 max 4
;		server	 192.168.0.100 ; port 1234
;		root-dir "/home/dk/fcgi/"
	]
] 

what is server ip and rootdir here?
Dockimbel
5-Jul-2007
[1857x2]
No, these parameters are not yet used. This page explains how it 
to make Cheyenne work with PHP : http://softinnov.org/cheyenne/blog.cgi?view=0005
Pekr, does it work now ?
Pekr
5-Jul-2007
[1859x2]
there is no localhost section in my httpd.cfg
Doc, why do I need to set-up full path? That limits usage on USB 
stick for e.g., simply moving Cheyenne around. Is it because of PHP?
Dockimbel
5-Jul-2007
[1861]
Because, the interfacing with PHP is still under development and 
lacks full path resolution in mod-fastcgi. Remember, that the PHP 
support is not a production-level feature, it's in alpha stage !
Pekr
5-Jul-2007
[1862x2]
well, does not work either .... :-)
I run php-cgi -b 999 and also set root-dir to full path ....
Dockimbel
5-Jul-2007
[1864x7]
did you uncomment the 'fastcgi lines in httpd.cfg ?
This one :
;	fastcgi
in modules section have to be uncommented.
check also that this other line is not commented :
bind fastcgi to [.php .php3 .php4]
Btw, it's php-cgi -b 9999 (not 999)