Articles delegate-en/4020-4030 of [1-5169] on the server localhost:119
  upper oldest olders older1 this newer1 newers latest
search
[Top/Up] [oldest] - [Older+chunk] - [Newer+chunk] - [newest + Check]
range 4020 - 4030   digest:
Testing the HTTP/HTTPS and FTP Delegate proxy
  07/29-16:31 . 4020  feedback@delegate.org (Yutaka Sato) [70]
___ Hi, You are asking somewhat unsupported or unspecified feature rathar than a bug. The AUTHORIZER parameter, if not used as a MOUNT option, is for a DeleGate as an origin FTP server not as a FTP prox
customization builtin messages and icons.
  07/29-19:51 . 4021  feedback@delegate.org (Yutaka Sato) [48]
___ Hi, You seem using old version of DeleGate as HTTPS server which could be heavy and slow in HTTPS/SSL gateway. Anyway it seem that MOUNT for /-/builtin/ does not work with HTTPS even in the current
Testing the HTTP/HTTPS and FTP Delegate proxy
  07/29-22:08 . 4022  "Jean Aumont" <pvahqbdyi-ecr676uuso5r.ml@ml.delegate.org> [259]
___ Hi Yukata, Thanks again for your response. My goal is to create a configuration file for the Delegate ftp proxy server that can support 3 requirements: 1) Acess a specific FTP server without UID/PWD
  07/30-00:44 . 4023  feedback@delegate.org (Yutaka Sato) [72]
___ Hi, As I wrote, DeleGate as a FTP proxy does not support AUTHORIZER which are not in MOUNT option. In short, in FTP proxy, the destiantion The enclosed patch is a very tentative implementation of it
  07/30-08:45 . 4024  feedback@delegate.org (Yutaka Sato) [62]
___ Hi, Here is an another solution. Your AUHTORIZER parameters can be unified into a single one as this: AUTHORIZER="-list{u1:p1,u2:p2},-list{u1,u2}(-reject.badpass),-any(others)" In the first -list, u
customization builtin messages and icons.
  07/30-09:54 . 4025  "David Wang" <pomhqbdyi-ecr676uuso5r.ml@ml.delegate.org> [79]
___ Hi Yutaka, Our current verison is 9.1.1, what did you mean this version "could be heavy and slow in HTTPS/SSL gateway"? Can I have its details? And if we'd like to MOUNT /-/builtin with https, which
  07/30-15:39 . 4026  feedback@delegate.org (Yutaka Sato) [27]
___ See the home page of DeleGate, especially the release information as <URL:http://www.delegate.org/mail-lists/delegate-en/3735> The current stable version is, as announced in the home page, 9.7.7 but
Use the same outgoing IP address as the incoming IP address
  07/31-05:12 . 4027  Sorin Esanu <pgagqbdyi-ecr676uuso5r.ml@ml.delegate.org> [12]
___ Hello, I run delegate (http proxy)on a multihomed linux server. Although delegate listens to all ips, the outgoing ip is always the main ip of the computer. Is it possible for delegate to use as out
  07/31-05:53 . 4028  feedback@delegate.org (Yutaka Sato) [22]
___ Why you need to do so? As long as I underdstand, an application program like DeleGate can't select the route to the destination server. You can select the source address of an outgoing connection by
  07/31-06:23 . 4029  Sorin Esanu <pgagqbdyi-ecr676uuso5r.ml@ml.delegate.org> [36]
___ Those 3 ips have different routes to world wide internet. So the application program does not have to select anything in respect to routes to destination servers. This is done by the hardware that r
  07/31-07:50 . 4030  feedback@delegate.org (Yutaka Sato) [65]
___ Wow, do you really have such number of interfaces on a machine? With the enclosed patch, you can use the following options to bind the source address of an outgoing connection to the address of inco
  admin search upper oldest olders older1 this newer1 newers latest
[Top/Up] [oldest] - [Older+chunk] - [Newer+chunk] - [newest + Check]
Generated:09/19 09:47:25 (1 sec) Expires:09/19 15:47:24 @_@V