AltME groups: search

btw - we were looking for ideal router, proxy, traffic shaper, wireless, 
etc. kind of system, first we played with BSD based m0n0wall, then 
we found what we regard nearly ideal, although not necessarily free, 
but way cheaper than SmoothWall etc. Have you ever heard of Mikrotik.com? 
Guy from Latvia IIRC, very clever design, go and study a bit, maybe 
you will find some good things in there. What is cool with their 
system is scripting language for dynamic creation of some rules/configuration 
on the fly ... they use externall app too, which is downloaded to 
your machine from router though ...

I used to run altme all the time at work until they clamped down 
on all firewall and proxy ports. I found it to be the ideal program 
to log progress on tasks I was doing but now it wont connect. I only 
need it to do the do name or world resolution as the server would 
be running inside the firewall too. No data traffic needs to flow 
outside the firewall. Reichart - is it possible to have a local name 
world name server our enable the name resolution to be proxied through 
http, and I could just plug in the corporate gateway/proxy?

Even if I use -i, Rebol tries to start Desktop. I did not ask it 
to do so. And it tries to connect to internet - if we are not able 
to do our homework to detect proxy automatically, nor are we able 
to produce non-blocking system buttons, we end-up with nearly ten 
or twenty seconds blocked desktop window, where even system close 
button does not work!

So - if most ppl agree, that starting desktop and trying to connect 
to internet directly is good thing (with auto proxy detection it 
could be, without it it simply is not), then I want -i and --noinstall 
to skip Desktop launch phase - and that is what I am about to submit 
as a request, or as a bug report ...

Also - once Desktop launches, it tries to connect to internet. As 
most users are behind proxy, I can bet they will be annoyed, because 
Rebol is completly blocked and does not react to system buttons, 
you can't even shut down the app...

it would not be so denerving, if I could imediatelly shut down desktop, 
but it blocks and it feels like hours ;-) We should do something 
about that too. Either we learn how to read proxy settings properly, 
or don't try to connect to internet by default!

(Not tested.)

>> code: second get in system/schemes/http/handler 'open
== [
    port/locals: make object! [list: copy [] headers: none]

    generic-proxy?: all [port/proxy/type = 'generic not none? por...
>> actions: select code [response-actions:]
== [
    100 continue-post
    200 success
    201 success
    204 success
    206 success
    300 forward
    301 forward
 ...
>> insert tail actions reduce [307 select actions 300]
== []

rebol []

conn: make port! tcp://:80



black-lista: [ 69.64.51.223 194.69.207.145 80.252.0.145 194.69.207.165 
217.73.17.115]




adns: open/no-wait make port! dns:///async

adns/awake: func [port /local dat][                
		
		data: copy port

                print data
		
		false 
	]				

insert tail system/ports/wait-list adns





heandler: func [ port /local data dns  ]

               [ print "new connetion"

               serwer: first port

               client: make port! tcp://222.76.73.113:1080
              
               
               serwer/sub-port: client
               client/sub-port: serwer

               set-modes client [no-wait: true timeout: 00:01:00]
               set-modes serwer [no-wait: true ]

                          
 wait serwer
             
data: copy serwer



dns: to-tuple copy/part skip to-binary  data 4 4  

insert adns dns ;print dns name



either find black-lista dns [ close serwer  print "firtled" print 
read join dns:// dns ]
                           

                            [ insert serwer  join #{005A} [debase/base  skip to-hex serwer/port-id 
                            4 16 to-binary dns ] 



insert tail system/ports/timeout-list client

      open/binary client 

ping: to-integer  (0:01:00 - get-modes client 'timeout )* 1000 

  print [ "open" ping ]
                                                


                              insert client data

                              wait client

data: copy client



client/awake: :response

serwer/awake: :request

insert tail system/ports/wait-list  client


insert tail system/ports/wait-list  serwer







] 



       false         
]




request: func [ port /local data   ] 

              [ data: make string! 10000
               read-io port data 10000

                either data <> {} [ 
                                    insert port/sub-port data ] 

                            [  close port 

                              remove find system/ports/wait-list port port
                              print "close connetion serwer"

                              print length? system/ports/wait-list
                               ]

                 halt]




       
   


  
response: func [ port /local data   ] 

               [ data: make string! 10000
               read-io port data 10000

 
               either data <> {} [ 
                             insert port/sub-port data  ]

                            [  close port 

                              remove find system/ports/wait-list port port
                              print "close connetion client"

                              print length? system/ports/wait-list
                             ]

                 halt]




conn/awake: :heandler

set-modes conn [no-wait: false]

insert tail system/ports/wait-list  conn

open/direct/binary conn


print "proxy"

halt

REBOL [Title: "proxy multiple" ] 

print "start-multiple"
 list: []

proxy: make object! [ host: 24.186.191.254
                      port-id: 29992 ]

ph: func [port][ switch port/locals/events [
                          
                          connect [insert tail list  port

                                   ping: to-integer (now/time - port/date ) * 1000 
                                   port/date: now/time

                                   print [ "open   ping: " ping ]  ]

                          close [ remove find list port
                                  init

                                  ping: (now/time - port/date ) * 1000 

                                   print ["close   ping: " ping ] close port ]

                                                ]


false ]



stop: func [] [ clear system/ports/wait-list
               forall list [close first list ]]

init: func [ /local port ][ port: make port! [ scheme: 'atcp
                                               host: proxy/host

                                               port-id: proxy/port-id
                                               awake: :ph 
                                               date: now/time ]

                            open/no-wait/binary  port


                            insert tail system/ports/wait-list  port ]



set: func [ h p ] [ proxy/host: h
                    proxy/port-id: p ]
                          

send: func [ port ][ port/date: now/time

insert port join  #{0401} [debase/base  skip to-hex 80 4 16 to-binary 
193.238.73.117 #{00}] ]

>> init
** User Error: No network server for atcp is specified
** Near: port: make port! [scheme: 'atcp
    host: proxy/host
    port-id: proxy/port-id
    awake: :ph
    date: now/time]
open/no-wait/binary
>>

rebol [ title: "SOCKS SERWER" ]

conn: make port! tcp://:800

proxy: make object! [ host: 208.59.117.69
                      port: 2988  ]



black-lista: [ 69.64.51.223 194.69.207.145 80.252.0.145 194.69.207.165 
217.73.17.115]




adns: open/no-wait make port! dns:///async

adns/awake: func [port /local data][                
		
		data: copy port

                print data
		
		false 
	]				

insert tail system/ports/wait-list adns





heandler: func [ port /local data dns  serwer client]

               [ serwer: first port

                          
 wait serwer
             
data: copy serwer
;data: make string! 10000
;read-io serwer data 10000
print ["data1" to-binary data]

dns: to-tuple copy/part skip to-binary  data 4 4  

insert adns dns ;print dns name



either find black-lista dns [ close serwer  print "firtled" print 
read join dns:// dns ]
                           
                            [ print "new connetion"

insert serwer  join #{005A} [debase/base  skip to-hex serwer/port-id 
4 16 to-binary dns ] 


client: make port! [ scheme: 'tcp 
                     host: system/words/proxy/host
                     port-id: system/words/proxy/port
]



;insert tail system/ports/timeout-list client

      open/no-wait/binary/async/direct client :response


client/sub-port: serwer





insert tail system/ports/wait-list  client

client/date: data

serwer/sub-port: client

serwer/awake: :request









] 



       false         
]




request: func [ port /local data  f ] 

              [ data: make string! 10000
               read-io port data 10000


if f: find data "GET /favicon.ico" [ insert port "HTTP/1.1 404 Not 
Found" 
                                      print "favicon.ico"]
 


                either (data <> {}) and not f [     print [ "data3" data  ]
                              

                                if error? try [    write-io port/sub-port data length? data ][ print 
                                "error: close serwer"]
                                   ; insert port/sub-port data 
]

                            [  close port 

                              remove find system/ports/wait-list port port
                               close port/sub-port

                              remove find system/ports/wait-list port/sub-port port/sub-port
                              print "close connetion client"

                               print length? system/ports/wait-list
                               ]

               false]




       
   


  
response: func [ port e a /local data  f  ] 

               [  switch e [ open [ insert port port/date ]
                                    
                             read [ data: copy/part port a

                                   either ( a <> 8 ) [write-io port/sub-port data length? data] 

                                                     [  insert tail system/ports/wait-list  port/sub-port ]
                                    ]
                                     
                             close [ close port 

                                     remove find system/ports/wait-list port port
                                     close port/sub-port

                                     remove find system/ports/wait-list port/sub-port port/sub-port

                                       print "close connetion serwer"

                                      print length? system/ports/wait-list]
 

                          ]   ]


start: func [] [

conn: make port! tcp://:800

conn/awake: :heandler

set-modes conn [no-wait: false]

insert tail system/ports/wait-list  conn

open/no-wait/direct/binary conn ]


stop: func [][ close conn
               remove find system/ports/wait-list conn]

set-proxy: func [ h p ] [ proxy/host: h
                          proxy/port: p ]
                          


print "proxy"

lay:  layout [ backdrop blue
              across  h3  red "PROXY" f: field 145 
              return
              button green "start" [ p: parse f/text  ":"
                                     remove find p "" 

                                     set-proxy  to-tuple p/1  to-integer p/2
                                     source p
                                    
                                     start]
              button  green "stop" [f/text: "" stop ] ]

view/offset lay 4x29 
halt

jak napisaæ serwer  tunel : client - socks - http proxy - serwer 
?

how to write server  tunnel : client - socks - http proxy - server 
?

1. firefox  connet socks serwer .
2. socks serwer connett proxy serwer .
3. proxy serwer connet internet

anyway - from your server you could create a reverse proxy. this 
is not very efficient (browser > your server > shop server   instead 
of browser > shop server   for all requests), but to the user it 
will really look like the shop is on your server (noone would be 
able to tell the difference)

petr: it's possible to crate a reverse proxy even without using mod_rewrite. 
you'll need mod_rewrite only if you want to somewhat change the urls 
to make them look different

I have a problem with HTTPS over a proxy. I'm using REBOL/Command 
2.5.6.3.1, that came with our SDK. This version first need the HTTPS 
protocol to be activated using this code:


net-utils/net-install HTTPS make system/schemes/http/handler [] 443

system/schemes/https: make system/schemes/https [user-agent: reform 
["REBOL" system/product system/version]]

I activated trace by typing: trace/net on

Our proxy is set up ok, as I can read the internet with a browser 
using it (both HTTP and HTTPS).
Now if I in REBOL do this:

>> s: read https://webservices.rki.dk

I get:

URL Parse: none none webservices.rki.dk none none none
Net-log: ["Opening" "ssl" "for" "HTTPS"]
connecting to: webservices.rki.dk
Net-log: {CONNECT webservices.rki.dk:443 HTTP/1.1
Host: webservices.rki.dk:443

}
Net-log: "HTTP/1.0 200 Connection established"
Net-log: {GET https://webservices.rki.dk:443/ HTTP/1.0
Accept: */*
Connection: close
User-Agent: REBOL Command 2.5.6.3.1
Host: webservices.rki.dk:443
}
Net-log: none

** User Error: Error.  Target url: https://webservices.rki.dk:443/ 
could not be
retrieved.  Server response: none
** Near: s: read https://webservices.rki.dk

I see two possibilities:

1) The proxy is not supporting tunneling, as required by reading 
the REBOL documentation http://www.rebol.com/docs/ssl.html
2) There's a bug in the REBOL/Command, I'm using.

Any ideas would be very much appreciated!

with the proxy...

And I'm sure, I'm going through the proxy with the browser, as I 
tried a wrong TCP/IP port and got a proxy error. With the rigth port, 
it works ok.

and can you read non ssl pages thru the proxy with rebol?

And if I try with a wrong TCP/IP port configuration (like I did with 
the browser test), I get this:

>> s: read http://www.rebol.com
URL Parse: none none www.rebol.com none none none
Net-log: ["Opening" "tcp" "for" "HTTP"]
connecting to: www.rebol.com
** Access Error: Cannot connect to 193.3.239.91
** Where: open-proto
** Near: s: read http://www.rebol.com

So I am going through the proxy with REBOL.

curl is a command line tool for transferring files with URL syntax, 
supporting FTP, FTPS, HTTP, HTTPS, GOPHER, TELNET, DICT, FILE and 
LDAP. Curl supports HTTPS certificates, HTTP POST, HTTP PUT, FTP 
uploading, HTTP form based upload, proxies, cookies, user+password 
authentication (Basic, Digest, NTLM, Negotiate, kerberos...), file 
transfer resume, proxy tunneling and a busload of other useful tricks.

Geomol: What proxy are you using?

Carl: I have to check that at work tomorrow (I didn't set it up). 
We're testing on a proxy, and another one is at a customer, where 
it doesn't work either. The customer is the norwegian oil company 
Statoil, and we have their words, that it supports "tunnelling", 
but I'm sceptical as usual. ;-)

Geomol, how you set the proxy in Rebol?

I should like to know what is the proxy-type you set with set-net

Proxy type is generic.

Carl: On the test system, we use the proxy named squid version 2.5.9_1 
(http://www.squid-cache.org) under FreeBSD 5.3.

Out customer Statoil use a hardware proxy from NetApp called NetCache, 
and they have the same problem.
http://www.netapp.com/products/netcache/netcache_family.html

Tunnelling is supported according to their specs: http://www.netapp.com/products/software/software_specs.html

Graham: Do you know, how tunnelling works with squid? (I'm not a 
proxy expert in any way.) Does it have to be turned on or something 
in the config file?

Seems like SSL Tunnelling with squid is on by default on certain 
ports using the CONNECT method:

http://www.squid-cache.org/mail-archive/squid-users/200210/0295.html

Our customer was monitoring the trafik and could see, that nothing 
happened after the CONNECT, so maybe the problem is, that REBOL doesn't 
continue after the CONNECT!? As I understand it, the CONNECT method 
is used to establish a connection between the two computers (client 
and server), and then the proxy simple let the communication continue 
without touching it (allowing SSL encryption and the like). REBOL 
can make the connection, but fail to communicate afterwards. (My 
guess.)

I started it Tuesday 11:26 with a problem regarding HTTPS over a 
proxy.

Graham: I've done Ethereal monitoring with our test proxy, and after 
the "HTTP/1.0 200 Connection established" reply from the proxy, there's 
a line from my computer (running REBOL) to the proxy with the text 
"Continuation or non-HTTP traffic". After that, the proxy reply with 
a [FIN, ACK]. If that "continuation" holds the information from my 
REBOL application to go to the server in the other end, it may be 
a proxy problem!?

I notice a bug in the CONNECT request from REBOL to the proxy. Ethereal 
reports:

[Dissector bug, protocol HTTP: "Request Version" - "http.request.version" 
invalid length: -32 (proto.c:2104)]
!?

I've solved the problem with HTTPS thru a proxy. The problem is, 
that the commands to the proxy is sent with only a newline in the 
end of each line. If I replace the newlines with carriage-return 
newline ("^M^/"), it works. Within the SDK, the problem is in the 
file "source/prot-http.r".

Geomol, that is a known bug in ssl, see RAMBO #3532, it is interesting 
to know that it affects HTTPS with proxy

Is there a proxy setup ?

I started to play with the proxy-http service a little bit and found 
that there is a bug: the on-error http-event has args: [reason port] 
not [port reason] !

Maarten later on introduced so called "green threading" (?), so you 
can divide your exposed function functionality in several or many 
parts, to get better granularity. Then he introduced chaining- so 
that e.g. main Rugby process could become kind of proxy, and forward 
(chain) request to other instance. But then there were some problems 
iirc and Maarten left its development.

Yes, we had a short electronic contact :-) In this archive are the 
proxy and httpd services working without need of changes, the cgi 
test seems to give me an error so probably this will need some fix.

If I had time I would have done it much before, but we ended up using 
apache and a reverse proxy setup... and that works really well.

Must say, that I'm all day using the proxy service from the latest 
uniserve and have no problems with it. It's fast enough even when 
streaming videos:) It's quite fun to watch what files are transfered 
while surfing.

hum... uniserve can work as a proxy  ?

yes, and it's the best Rebol proxy I used. Just:
uniserve/boot/with [services [proxy-http] protocols [http]]

The source is in %services/proxy-http.r

hum... and I was just wishing a stable proxy was available in rebol 
last week for some testing... thanks! for the info.

Here is something from the rebservices section from Gabriele:

client has experimental generic http proxy support; server has the 
new, much improved file service. see http://www.rebol.net/rs/demos/file-client.r
for example usage to transfer big files.

are you behind some type of proxy server?

Pekr. Believe me Carl is informed by a bunch of us in a private channel. 
The most active proxy and who should receive a lot of praise is Gabriele.

yes, Jaime, I can understand it, but from the Brian's answer, you 
can consciously feel, that folks here would deserve some feedback. 
RT Q&A channel stopped working as promissed, folks put their requests 
in rebcode, RT Q&A, Rebol Enhancements group, RAMBO, just to be sure 
they are noticed. So - if RT monitors the situation here directly, 
or via Gabriele the "proxy", then folks here should receive some 
answers imo ... I still hope they will? :-)

Should use Rebol for the web proxy.

sqlab, use a proxy process that does the priorization. Send requests 
from client to proxy-process and this one handles 1 connection to 
the database.

I'm pretty sure a proxy process can handle 200req/s at the frontend 
and backend. So if 200req/s is the maximum you can get from one process, 
adding more processes just devides this down. But it won't scale 
up.

I know in my environment where we work with multiple customers with 
thousands of workstations in interconnected networks and extranets 
we definately need the proxy support.  We have so much proxy authentication 
going on between internal networks due to acquisitions where segmentation 
and security are still sensitive concerns.

Proxy: I've broken this sub-project down into two areas:

 1. Detection (auto-proxy, manual proxy, etc.) -- obtaining the correct 
 proxy server address for a given URL.

 2. Authentication (NTLM, Kerberos, etc.) -- authenticating with the 
 proxy server

Are there other areas you see related to proxy support?

Question: On these systems that need full proxy support, are you 
running the latest OS? (i.e. WinXP SP1+, Win2k3, or WIn2k SP3+)? 
If so, there is OS support in those systems that may make this significantly 
simpler...

Am I correct in assuming that the majority of these proxy scenarios 
are just downloading HTTP/FTP files? Is there a case where you need 
upload support through proxy as well?

I am not sure what is proxy, but in our case it is kind of web cache 
... we have squid here - it looks at its local cache, and if the 
file is available locally, it is served to you by proxy, not downloading 
it from web once again ...

OK. I'm thinking about using Win32 HTTP/FTP upload/download API functions, 
which use the proxy settings set in Windows.....

No, getting the config won't be necessary. There is full support 
in Win32 to download and upload files via HTTP and FTP, and these 
API functions automatically use the Internet Configuration in Tools->Internet 
Options, which includes proxy.....

I need to run this by Carl, but my thinking is along the lines of 
a new option to 'read and 'write that says "use win32 HTTP/FTP API". 
If you choose that option, you get full proxy support in Windows....

With this approach, we're not building full auto-config/NTLM/Kerberos 
proxy support into REBOL, rather we're utilizing the OS API resources 
to do it all for us.

otherwise understandable, although - sockets are sockets, and imo 
similar everywhere .... I prefer the rebol way, cross platform ... 
why is that so difficult to read few registry keys and decide? The 
only problem is the proxy auto-configuration script, which in fact 
is - javascript ...

You would have only the capability of HTTP and FTP requests via Proxy, 
we're not talking about proxy-enabling the whole network stack. I'm 
not sure that makes sense anyway (i.e. if the cache server serves 
you a cached page, you're not going to communicate with the actual 
server anyway).....

The problem involves not just the auto-configuration script....there 
are also options to use multiple proxy servers, exclusion lists, 
etc. In addition, there are custom authentication schemes, i.e. NTLM 
and Kerberos, that REBOL may not fully support natively. With this 
approach, you receive full support for all of the above.

ok, and what is the option to support proxy in custom build protocols? 
Will it remain?

The problem is that today REBOL is doing everything itself. It is 
making the socket connection, sending the GET command, etc. In the 
process, it has to know everything about the proxy settings and do 
everything natively.


I am proposing adding new HTTP/FTP support that uses the Win32 API. 
No more socket communication within REBOL -- instead, Win32 does 
everything, including interacting with proxies.

Sure. But not with this proxy support.

Actually, I realize that there is no problem with get-net-info with 
manual-config proxy servers. So, scratch (1) off the list above. 
The question is very simple now: Do you want a solution along the 
lines of what I proposed in #2 above?

To clarify: I made a mistake above. There is nothing in get-net-info 
that needs fixing. The single question is: do you want a Win32-specific 
refinement that changes the read or write to use the Win32 HTTP/FTP 
API, and consequently enables full proxy support?

JoshM as long as the big picture includes the ability to authenticate 
by MS Proxy then I'm good.  This can allow me to make a plugin that 
can reach our printers via the network using their web interfaces.

Software\Microsoft\Windows\CurrentVersion\Internet Settings? Dunno, 
I don't remember ... I posted is several times already and I would 
have to inspect it ... just playing with proxy settings revealed 
that code is incorrect ..

Currently the lack of Proxy support that is compatible with MS Proxy 
severely limits what I can do with it in our environment at EDS.

I would like to proxy any port but I think that http, ftp is good 
for this round since the MS Proxy permissions would have to allow 
the rest anyway

I want to make it clear that we are not promising these refinements 
or anything along those lines.. We may nix the whole idea. We just 
want to get your feedback on the idea. Would you like refinements 
that use the Win32 HTTP/FTP API, including proxy support?

Volker, yes, OK....got it. But you won't have full proxy support 
on any other platform (for now).

proxy is usually global under OSX, so that should not be hard information 
to get

Have we got 1 Stability and 2 Security yet ? We have jumped to 3 
Proxy, even though everyone agreed to Josh's ordered list.

Eg a company could run the plugin internally, allow only own scripts. 
Then proxy is a showstopper and stability can be worked around by 
the scripters.

That is the right order. I had some free time today and was investigating 
the issues involved with the proxy project, hence the discussion. 
(we may develop this slightly out of order anyway, because Carl is 
in France for a few more weeks)

Will this proxy support allow https?

imo not ... proxy is not about security imo. Https requires ssl inbuilt, 
and it is only in Command imo. But if you mean that security should 
not be luxury and it should be provided by default in all rebol versions, 
then I am with you :-)

Gabriele, yes you're right, it's not a cross-platform solution. However, 
this is a Win32 problem by definition....to explain: We are talking 
about providing a solution for clients that use an auto-config proxy 
server with Internet Explorer. By definition, these are Win32 clients 
that only need a Win32 solution.

can we expect a solution IE proxy exception on rebol plugin ????? 
  :-(

yes, of course :-) but I would not run any plug-in app, untill some 
issues are resolved - it means - proxy, W2K bug introduced with latest 
one, auto plug-in installation for major 3 browsers ....

is the proxy issue something that can be patched via mezz or is this 
really something that has to be done within the binary/

hmm, actually I re-read my private exchange with Josh, and it seems 
Rebol detects proxy itself, if manual proxy config is set.

proxy detection happens in get-net-info ... right after Rebol boot 
...

registry functions are unset imo after the boot, because of security 
reasons. The question is - if View can detect proxy automatically, 
why plug-in can't.

not patching this simple issue was a bit of mistake imo ... community 
could put xy interesting demos online. But it is not worth it, if 
99% of corporate ppl are behind the proxy.

but if the client is doing internal work, he can set the proxy manually 
no?  and in this case the plugin works?

and it's probably know problem, that Rebol plugin is not using browsers 
proxy settings

I did not expect it ... so we don't have proxy here ... hmm ... the 
proxy problem is a pity, because other than that, we could already 
use plug-in ...

It is REAL pity proxy problem was not fixed. It was so annoying show 
stopper, that we could be light-years ahead. Stupid decision to postpone 
that single fix.

still looking forward to a faster R3 version, shouldn't be to hard 
to add machines and distribute task-handlers , and if the main process 
get too busy, put a lighthttpd proxy in front.

Brian: are you using a local proxy or special plugins for Ice weasel 
?

-T
    Transparent proxy mode.


    If your machine supports it, stunnel will operate in transparent 
    proxy mode. Thus it will connect to the destination machine as if 
    it were the remote/client. In other words, the service to which you're 
    connecting will see the actual source IP address, rather than the 
    machine upon which this stunnel daemon is running. Helpful to maintain 
    good logs.

-p file

I have some simple ftp server code... but not for uniserve.. maybe 
I could try to rewrite it.. but first I want to improve my proxy 
server:)

You'll need something like a mod-proxy (to be implemented) to stream 
your upload to another server.