AltME groups: search

Are the proxy settings in AltMe working? I tried to run AltMe from 
work by inserting the proxy settings but it fails to connect to the 
internet. The docs on the website would seem to suggest that there 
is no proxy but having them in the settings confused me.

other - lowering dekstop timeout - absolutly obtrusive experience 
trying to connect to internet, when you are behind the proxy. I would 
not connect by default

I've found THE LINE that Rebol hangs up on when the FTP server returns 
a 425 response.  It is the line with the ;<--- after it below:

	accept-connect: func [port type][
		if not port/locals/passive [
			either port/locals/listen-port [
				if type <> 'new-dir [
					port/sub-port: first port/locals/listen-port ;<---
				]
				close-listen port
				port/locals/listen-port: none
			][
				net-utils/accept-proxy port/sub-port
			]
		]
	]

does proxy setting apply even for https?

I need to read out a possible proxy config.

Which reminds me .. what will it take to add proxy support to R3's 
 tcp ?

what does it say when you try that line? maybe it's a faulty proxy

Hi, I just received reply from RT towards my following request:

----------

I have also suggestion towards View Desktop. IIRC there is also RAMBO 
entry about it - please, lower the timeout, because Desktop tries 
to connect to Internet by default, and if someone is behind the proxy, 
it is frustrating experience - you can't close blocked Rebol even 
by window close button. As for me, I would prefer not connecting 
by default, and changing "Local" to "Connect", "Disconnect" duo ...
--------------


On Viewtop, I agree.  Let's develop a good method for that, and put 
it in the
next release.


There are a few choices.  1) Shorter timeout, 2) popup request to 
connect,

3) connect on demand (after clicking on an icon that has no file).

Perhaps you know some users who have a suggestion?

-REBOL Support

as for desktop the best case would be to support proxy automatically, 
as planned for plug-in, but we don't know status of such a development. 
My opinion is not to connect to Internet by default, or just display 
dialog box asking, if we want to connect in the beginning?

hmm.. sounds like hooking up to another PHP as proxy

I'll betcha the problem is a proxy server.

Squid? It is proxy, no? Or FW?

well, from experience I know that Altme doesn't like proxy servers

last year DevCon... Carl mention one of their lessons learnt from 
IOS is that sometimes encrypted message may contain 'dirty characters'...that 
can be rejected by proxy, firewall etc.

'dirty' = 'non approved words...

and since they're at a school, they almost are certainly using a 
free proxy like squid.

I do not agree to its design in some basic stage - like having only 
one plug-in per page etc. Other things have to be decided BEFORE 
development starts .... e.g. how will you configure it (Flash does 
so with right-mouse click), but rebol has legitimate usage for right-mouse 
click. Proxy detection was not correct and now there is a question, 
if we should go and tunnel network communication using networking 
available to browser or not ...

Oh, the autoconfig wizard. You can ignore that error for now - it 
is probably caused by proxy settings or some such. As long as at 
least some of the seeders are poked through their NATs or otherwise 
visible to the net, you should still be able to download.

I really don't undersant why there is so many people crying... I 
have Uniserve runing for several months without problems, parsing 
about 50 pages two times per day to provide culture informations 
in the city I live, I use Rebol to build PHP sites, Flash apps, as 
a proxy server as, a clasic system console and for so many every 
day scripting and I really cannot imagine I would use something else 
than Rebol for such a job. And if you still think that you cannot 
do anything in R2 and have to wait for R3 to start, you can take 
a look for other technology. With computer languages it's same like 
with normal languages - the more languages you know, the better you 
are.

But - one thing worries me anyway - R3 http scheme is out for how 
long - 2 years? And we don't even have proxy for it. Not to mention 
other protocols. So if we (community) can't find some time to do 
other schemes, where's our help then? The thing is, that schemes 
stuff is really difficult. I can imagine myself doing some easy styles, 
but surely not complex thing as network protocols :-(

Pekr, this example with proxy, we see things differently. As I read 
your words, you're complaining, we don't have proxy for the http 
scheme (after maybe 2 years). I can only talk for myself, but the 
reason, why I don't look into things like that, is because it's way 
down on Carl's list (maybe third or fourth priority). I would like 
to see the first levels bug-free and stable, before I move on. (And 
you don't hear me complain about proxy. :-) )

A server-side scripting language which cannot handle literal strings 
- and especially one that claims to be Unicode - has to be excluded 
from consideration for templating web content which is expressed 
in any other langauge which uses curly braces.  I told BrianH that 
the red flag here should be Tcl as Rebol shares this with Tcl.  Literal 
string are literal strings.  Period.  No if's and's or "that might 
be my curly brace in there" ...  Unless you dream of a Rebol-only 
world - and that fantasy should have passed some years back.    This 
falls under the heading of folly - a topic too often neglected.  
Folly in a meritocracy usually requires some individual to speak 
up.  But the folly of meritocracies is that  to be heard taht individual 
would already have to be playing within those constraints.  We see 
this in schools which graduate top people distinguished for inidividual 
effort who then do not fit well into teams.  They did group work 
in college by being the one who saved the group from failure by ... 
their individual effort.  For me this will be what makes or breaks 
my involvement with REBOL.  I could not wait for REBOL4 and hope 
for change then by getting into the merit circle.  My outside voice 
would have to be heard before it is too late. Tcl as the do-all is 
folly.  As nuch as I admire OOTcl, the XOTcl IDE and Expect.  I cannot 
use Tcl with "balanced brace" foolishness.  Of course if we all adopt 
XML and abandon scripting in non-XML languages ... So  We have comment 
{  }  and that was a mistake: it should have been symmetrical as 
in c{ comment here as literal with } or whatever }c   And that is 
water under the bridge.  We cannot be UNICODE and claim that  we 
must escape a certain pair  of characters if ithey are in a literal 
string.  That is silly. Ludicrous. Folly.  A literal string is a 
data value where you do not get to peek.  Imagine a proxy object 
that said: "I will be your proxy only if you promise that when the 
real object appears it does not contain [ folly happens here ] " 
  Many forms of "catch-22" in the world of beaurocratic regulation 
have a similar pattern.  I am no expert on unintended consequences, 
but requiring that some pair of characters be escaped in otherwise 
literal content has consequences for TEMPLATE value TEMPLATE  There 
should be a lesson there: some markup must be arbitrary and the choice 
will matter.  { and } are the wrong choice.  At least the terminal 
markup must be "sacrificed (it will always have to be escaped so 
pick carefully.   [{ is a bad combo for JSON so #[{ looks worrisome 
to me.  I propose lit |ls# and_content_then  #ls|    Someone shoots 
that down and we inch towards a suitable result.  Not perfect.  But 
usable.  { and } are not useable in the real world on the server-side 
if rebol is to play a role with other languages.  Play nice.  Please.

well, i have some fun coding a proxy for R3 since some days, but 
I reach my limit attention

What do you mean by completness? IMO R3 is more advanced than R2 
already, and we are nearing beta stage =  system architecture is 
in-there, all slots in the right place. Now we need to finish few 
things, for user to be usable as R2 is:


- better console (not necessarily needed, but Windows one is total 
crap and makes experience 40% worse for me)
- fixed call
- network protocols (ftp, pop, smtp, proxy )
- ported DB drivers (done by community hopefully)

- improved parse (needed probably if we want to have DB drivers and 
network drivers done new way, but not necessarily)
- missing CGI mode
- GUI far from beta

BrianH: it is not about wasting. I just want we don't do fatal mistake 
- pretending we order users how they should use R3. R3 would be already 
used by many ppl, but is not, due of following reasons:

- missing network protocols, proxy
- call incompletness in comparison to R2
- weird console
- missing CGI mode
- missing DB protocols


No matter how your module system is usefull, if we don't provide 
users with R2 level completness, we are doing fatal mistake ...

as for networking - no, what I had in mind is networking schemes 
- we do have only http 1.1, no proxy, no smtp, no pop3, no ftp, etc

This is the STunnel example doc for https .. the webmaster at the 
top doesn't recommend it that much ... http://www.stunnel.org/examples/https_windows.html


This shows nginx with separate  ssl usage and also using it as reverse 
proxy (with load balancing also)  http://www.linuxjournal.com/article/10108

SSL

server {
  listen   127.0.0.1:443;
  server_name  secure;
  access_log  /var/log/nginx/secure.access.log;
  error_log  /var/log/nginx/secure.error.log;
  ssl on;
  ssl_certificate /etc/nginx/ssl/server.crt;  
  ssl_certificate_key /etc/nginx/ssl/server.key;  
  location / {
    root   /var/www/secure;
    index  index.html index.htm;
  }
}

LOAD BALACER 
upstream python_servers {
  server 127.0.0.1:8001;
  server 127.0.0.1:8002;
}
server {
  listen   127.0.0.1:8000;
  server_name  proxy;
  access_log  /var/log/nginx/proxy.access.log;
  error_log /var/log/nginx/proxy.error.log;
  location / {
    proxy_pass http://python_servers;
  }
}

--

Both seem logical and if combining ssl + proxy (server part) them 
would work I would get what I need

I use apache2-MPM as a reverse proxy in front of Cheyenne for the 
same reasons (static serving, ssl), works flawlessly, but now is 
time to move to nginx. Looking at MacPorts variants for nginx, there 
are many options that I see interestings:
root/trunk/build alpha% port variants nginx
nginx has the variants:
	dav: Add WebDAV support to server
	flv: Add FLV (Flash Video) streaming support to server
	mail: Add IMAP4/POP3 mail proxy support

 ssl: Add SSL (HTTPS) support to the server, and also to the mail 
 proxy if that is enabled
	status: Add /nginx_status support to the server

 perl5: Add perl support to the server directly within nginx and call 
 perl via SSI
	realip: Using nginx as a backend
	addition: Append text to pages
	substitution: Replace text in pages

 gzip_static: Avoids compressing the same file each time it is requested

 google_perftools: Enable Google Performance Tools profiling for workers

 upload: Enable Valery Kholodkov's upload module (http://grid.net.ru/nginx/upload.en.html)
	universal: Build for multiple architectures

now I need to make it reverse proxy to cebelca

I use lighttpd and reverse proxy to Cheyenne. Works great.

Petr, in any case, you can "extend" Cheyenne feature-set by using 
a front reverse-proxy (nginx, lighthttpd, stunnel, apache,...).

it was quite simple , I just joined two examples from their tutorials 
.. the SSL and the reverse proxy one .. I can give you the config 
file

how I use it: nginx get all the requests, if a file is not found 
it will proxy-reverse the request to cheyenne wich is configured 
with a on-status-code [404 trap.r] . trap.r check the url request 
and either load and respond with an rsp or send a 404

I run Cheyenne as reverse proxy, which works very well.

If security is a big concern, I would rather use a C-based filter 
proxy or an IDS tool like Snort (requires careful configuration to 
avoid too much false alarms).

Ideally, I guess all the socket control scripting should be done 
within the 'socket-app.

I was thinking this would make a great proxy to a remote server for 
futher processing... but how to pass the arguments?

Here's a modified on-message from ws-test-app.r 

	on-message: func [client data][						
		;send data
					
		do-task/on-done data func [client data][	 
		

   ;data: do/args %/c/cheyenne/cheyenne/test.r {one "two three"}		  
       ;doing a script passing /args

   data: read http://www.php.net/usage.php				      ;as 
   a proxy to PHP server
			
			send/with data client
		]
	]

... CSS, database access, acting as a proxy to servers, JQuery, Google 
map integration, Amazon S3, OpenID, AtomAPI and other RSS integration, 
Delicious... man, i HATE that stuff.

All in all doc, cheyenne sockets are very impressive. 
Couple of suggestions.. 

- Have a folder specifically for socket-apps that automatically get 
loaded into the http.conf file.. 

- Create a connection through PHP (if possible.. otherwise can just 
proxy, but adds lag)

(It pipes all R3 Chat connections via a CGI proxy.)

Here's some code that uses flash as a websocket proxy for browsers 
that don't support websockets
http://github.com/gimite/web-socket-js

Needs some tweaking, particularly with ports.

POST /cgi-bin/rebdev HTTP/1.0
Accept: */*
Accept-Charset: utf-8
Host: host.rebol.net
User-Agent: REBOL
Content-Type: application/x-www-form-urlencoded; charset=utf-8
Content-Length: 56


[0.4.0 "Graham" password  login]HTTP/1.1 500 Internal error in REBOL 
CGI Proxy
Date: Sun, 14 Feb 2010 02:05:45 GMT
Server: Apache/2.0.53 (Fedora)
Content-Type: text/plain; charset=UTF-8
Via: 1.1 bc7
Connection: close

Cannot connect (3)

Anyone got some quick instructions on how to use Nginx as a proxy 
for Cheyenne?

I use something like this in my nginx config:
        location ~ \.(rsp|cgi)$ {
            proxy_pass   http://lucya.desajn.web:8080;
            
            proxy_set_header   X-Real-IP        $remote_addr;

            proxy_set_header   X-Forwarded-For  $proxy_add_x_forwarded_for;
            proxy_set_header   X-URI $request_uri;

            proxy_set_header   if-modified-since $http_if_modified_since;
            
			client_max_body_size       10m;
            client_body_buffer_size    128k;

            proxy_connect_timeout      90;
            proxy_send_timeout         90;
            proxy_read_timeout         90;

            proxy_buffer_size          4k;
            proxy_buffers              4 32k;
            proxy_busy_buffers_size    64k;
            proxy_temp_file_write_size 64k;
        }

I can access a websocket page from the interweb, but the socket communcations 
isn't working at all? However, it works fine accessing on the local 
network? Any ideas?

 Is there any HTTP proxy in between? Does it require SSL? Cheyenne 
 current websocket implementation doesn't support HTTPS yet.

 Is there any HTTP proxy in between? Does it require SSL?
 - No proxy, no ssl.

if you have nginx in front you can have cheyenne servers reverse 
proxied to many ip-s yes.. in the same way you can for different 
subdomains or domains  (rule for reverse proxy is very simple)

Or use Nginx as a reverse proxy to Cheyenne.

and i had to be aware where are they checking out the source of the 
projects they were working on and i also had to assign port numbers 
to them, so i could configure the reverse proxy in apache/nginx to 
connect to their app servers

You could do the same (reverse proxy/nginx) with Cheyenne instances.

hmm... ok, i step back and think about it. thx, for ringing the complexity 
alarm! :)


on the other hand, i just saw there is https://github.com/nodejitsu/node-http-proxy
which is a reverse proxy for nodejs.

if u remember, i was missing this functionality from cheyenne too.


i think what carl was aiming w rebol is happening w javascript / 
json now...
it's not as advanced as rebol, though, but it's

No, NginX is the reverse proxy for Cheyenne (and Fossil). Several 
people here went before me

I see the expected result in R2.7.6:
>> print read dns://www.rebol.com
205.134.252.23
>> print read dns://205.134.252.23
www.rebol.com

Maybe you have a firewall, proxy server, etc?

As you say, the ip address is correct.  but  I didn't use a firewall 
,nor  a proxy . I think  the problem  comes from my ISP

There was an end-of-line problem in the SDK, when using HTTPS with 
a generic proxy. Packets were sent with just LF, where the definition 
(RFC 2616) say, CRLF should be used. It could be fixed in the SDK 
by editing prot-http.r. I haven't checked, if this is fixed in later 
versions (incl. View/2.7.7), so it's a potential problem.

Overall R3 should have a /Library interface. IMO adding a way to 
Rebol so that more c-ish datatype can be handled would make life 
a lot easier. And of course, provide a way to handle callbacks. Maybe 
via a proxy stub on the C side that transforms these callbacks to 
TCP socket requests.

Offered by:
	TomBon
Task:

 R3 - Bindings for libcurl - the multiprotocol file transfer library
	http://curl.haxx.se/libcurl/

	C - API  -> http://curl.haxx.se/libcurl/c/allfuncs.html


  libcurl is a free and easy-to-use client-side URL transfer library, 

 supporting DICT, FILE, FTP, FTPS, GOPHER, HTTP, HTTPS, IMAP, IMAPS, 

 LDAP, LDAPS, POP3, POP3S, RTMP, RTSP, SCP, SFTP, SMTP, SMTPS, TELNET 

 and TFTP. libcurl supports SSL certificates, HTTP POST, HTTP PUT, 

 FTP uploading, HTTP form based upload, proxies, cookies, user+password 

 authentication (Basic, Digest, NTLM, Negotiate, Kerberos), file transfer 
	resume, http proxy tunneling and more!


 libcurl is highly portable, it builds and works identically on numerous 
 platforms, 

 including Solaris, NetBSD, FreeBSD, OpenBSD, Darwin, HPUX, IRIX, 
 AIX, Tru64, Linux, 

 UnixWare, HURD, Windows, Amiga, OS/2, BeOs, Mac OS X, Ultrix, QNX, 
 OpenVMS, RISC OS, 
	Novell NetWare, DOS and more... 

Amount:
	$150
Valid until:
	01.11.2010
Terms:
	PayPal

Just remembering my Cerebrus pop proxy anti-spam script .. I had 
both progress meters for both messages download and message download

we can use a proxy actor

Does proxy support require work at the C level?

in my opinion, R3 is already useable, apart from GUI, maybe pop, 
ftp, proxy support (nowadays I don't need it though), and ugly console 
:-)

Is there any reason why proxy is not implemented? Should it be part 
of http scheme or should be intermediate scheme? ie http -> proxy 
-> tcp. Where is oplaned to save proxy settings in R3?

Kaj full respect to your effort, in the other hand the proxy seems 
not to be overcomplicated. it may be a good training task, in R2 
it has maybe 20 lines. question is if there is some architectual 
restriction (for example synchronous / asynchronous etc.)

I would add following "negatives" (depends upon how you look into 
it):


- no /libary extension and easy wrapping of DLLs. There was a bounty 
started to bring in kind of R2 DLL capabilities using extensions, 
Max was working on something, but did not deliver. Some ppl claim, 
that working with extensions is easy enough, much more powerfull, 
and that in fact R2 /library interface was weak in comparison in 
capabilities.


- weak and underpowered CALL.No /output or /wait parameter IIRC. 
Carl said, that R2 C code to it was complex, and that the code is 
eventually awailable for volunteer to bring in to R3. The outcome 
is - CALL is limited in usage in comparison to what can be easily 
achieved in R2.


- protocols. The only protocol IIRC was available was HTTP, done 
by Gabriele. It was HTTP 1.1 compatible, but due to some bug (?) 
it was downgraded to 1.0 version. No proxy support. Other protocols 
were done by some other ppl, I do remember Graham doing some work 
here. In regards to protocols, IIRC there was some work done by Kaj, 
who brought Curl networking extension to R3.


- under Windows console is a bit more inconvenient in usage than 
in R2, we use native Windows console, yet we don't have full console 
support, so we can't replace the native R3 one by e.g. Console2 or 
some other version ...


- DBAccess - forget R2 protocols available. The rescue is ODBC extension 
for R3


- CGI - no native CGI support in R3, though it should not be difficult 
to emulate


- Sorting & Unicode - althought we have Unicode strings available, 
sort is not adapted to that, and the question is, if it can be easily 
done ...

(by proxy) from Karl Robillard