Articles delegate-en/3570-3580 of [1-3976] on the server localhost:7119
  upper oldest olders older1 this newer1 newers latest
search
[Top/Up] [oldest] - [Older+chunk] - [Newer+chunk] - [newest + Check]
range 3570 - 3580   digest:
Antwort: Re: [DeleGate-En:3573] Antwort: Re: [DeleGate-En:3569] relative paths
  11/03-17:16 . 3570  feedback@delegate.org (Yutaka Sato) [45]
___ Hi, OK, I understand that you are using DeleGate as a gateway between HTTP cleints and a HTTPS server, reached via another HTTP proxy. Any URL of "https://..." in responses from the server must be r
DeleGate/9.3.0 (STABLE) -- new stable version
  11/07-22:10 . 3571  feedback@delegate.org (Yutaka Sato) [43]
___ Dear DeleGate users, I inform you of the new release of DeleGate available as follows: DeleGate/9.3.0 -- new stable version This is a new stable version of DeleGate with new features and many fixes
Question on switching upstream proxy based on port
  11/11-06:44 . 3572  "Tetsu Saiga" <p6qgqbdyi-l7lkx2ugranw.ml@delegate.org> [40]
___ Hi, I'm trying to have Delegrate run as a Application level router that will switch to either a HTTP proxy or SOCKS base on the port. If it's port 80 then it should use a HTTP proxy and SOCKS for ev
  11/11-08:22 . 3573  feedback@delegate.org (Yutaka Sato) [47]
___ Hi, As far as I remember, I've never announced that DeleGate supports relaying as a circuit level proxy as SOCKS and forwarding to an application level proxy as a HTTP proxy, although I've been inte
  11/11-13:15 . 3574  "Tetsu Saiga" <p6qgqbdyi-l7lkx2ugranw.ml@delegate.org> [60]
___ Thanks for the help! It works great. I did notice the protocol being the same when I tested without the "http://" in PROXY. Seems like you made PROXY flexible because I was able to do "PROXY=proto:/
Odd HTTP proxy caching retrieval behaviour
  11/11-14:13 . 3575  "Tetsu Saiga" <p6qgqbdyi-l7lkx2ugranw.ml@delegate.org> [154]
___ Hi, HTTP proxy caching is a bit odd. This is with version 9.3.0. The HTTP proxy runs with "delegated -P8080 SERVER=http CACHE=do". Files are cached but they do not get used after the same file is re
  11/12-04:31 . 3576  feedback@delegate.org (Yutaka Sato) [43]
___ This "(no-cache)" in the log means the request from the client indicated not to use the cache, maybe with "Pragma: no-cache" or "Cache-Control: max-age=0" or so which is issued with a "Reload button
  11/12-09:47 . 3577  "Tetsu Saiga" <p6qgqbdyi-l7lkx2ugranw.ml@delegate.org> [79]
___ You're right there's a "Cache-Control: no-cache". 1 GET xxxxxxxxxx HTTP/1.1 2 Content-Type: application/x-www-form-urlencoded 3 Keep-Alive: 300 4 User-Agent: xxxxx 5 Host: xxx.xxx.xxx.xxx 6 Cache-Co
DeleGate/9.3.1 (STABLE) -- a fix for SSL session cache with client's certificate
  11/14-19:12 . 3578  feedback@delegate.org (Yutaka Sato) [29]
___ Dear DeleGate users, I inform you of the new release of DeleGate available as follows: DeleGate/9.3.1 -- a fix for SSL session cache with client's certificate Fixed the server-side SSL session cache
about sockmux pipe
  11/15-14:22 . 3579  "feng yan" <p7mgqbdyi-l7lkx2ugranw.ml@delegate.org> [69]
___ hello,delegate.org I installed DG9.3.0 in Linux. run delegate ,follow: #mkfifo /tmp/rfifo #mkfifo /tmp/wfifo #./delegated SERVER=sockmux:commin@/tmp/rfifo SERVER=sockmux:commout@/tmp/wfifo PORT=9023
  11/15-14:48 . 3580  feedback@delegate.org (Yutaka Sato) [36]
___ Hi, It seems that I did break SockMux over FIFO, maybe in DeleGate9.2. You can escape the problem with a parameter as follows: SOXCONF=crypt:no I'll fix the problem in DeleGate9.4.0. Cheers, Yutaka
  admin search upper oldest olders older1 this newer1 newers latest
[Top/Up] [oldest] - [Older+chunk] - [Newer+chunk] - [newest + Check]
Generated:05/17 18:34:50 (0 sec) Expires:05/18 00:34:50 @_@V