Articles delegate-en/4800-4810 of [1-5033] on the server localhost:7119
  upper oldest olders older1 this newer1 newers latest
search
[Top/Up] [oldest] - [Older+chunk] - [Newer+chunk] - [newest + Check]
range 4800 - 4810   digest:
FTP to HTTP Protocol Translation Gateway
  05/07-02:08 . 4800  David Fogarty <pxyjabdyi-qghxypl2e3y6.ml@delegate.org> [53]
___ Hi Yutaka, Thank you for your quick and detailed response. You confirmed what I suspected. I will look for other means of accomplishing my goals. Thanks again, Dave Fogarty Senior System Administrat
Delegate 9.9.6 SFTP listing timeout
  05/07-13:42 . 4801  Vijay Pandit <pyejabdyi-qghxypl2e3y6.ml@delegate.org> [33]
___ Hello Yutaka, Using Delegate 9.9.6 as a FTP/SFTP proxy, and found that if there are a large number of files in the SFTP server folder, a directory listing times out after 30 sec and returns a empty
  05/08-14:15 . 4802  feedback@delegate.org (Yutaka Sato) [24]
___ Hi, It is as expected if the timeout is "60 seconds" and if there is a statement in a logfile as follows: 05/08 14:13:02.06 [27474] 1+0/2: --SFTP relay_list(ls -l ) slow (60.0) rdy=0 I'm not sure wh
yysh issues.
  05/12-18:06 . 4803  Corley Kinnane <pymjabdyi-qghxypl2e3y6.ml@delegate.org> [34]
___ Hi, I have been using Delegate on and off for years, mainly as an HTTP proxy and tcprelay tool. Recently I discovered the new yysh feature. It looks very promising. I tried using OpenVPN to a server
  05/13-03:04 . 4804  feedback@delegate.org (Yutaka Sato) [53]
___ Hi, Maybe you got nothing via it and saw a text cached in your browser. You should have seen what is wrong in the LOGFILE on the server side. In this case there should be "No permission" in your log
  05/13-03:34 . 4805  feedback@delegate.org (Yutaka Sato) [27]
___ If you mean a host name resolusion is not available on the YYSH server side, you should use the YYSH server as a SOCKS proxy rather than a HTTP proxy, and do the resolution at the client side with a
  05/13-16:43 . 4806  <pymjabdyi-qghxypl2e3y6.ml@delegate.org> [47]
___ On Thu, 13 May 2010 03:34:28 +0900 (JST), feedback@delegate.org (Yutaka The N900 uses its own DNS proxy by default so that when a connection is changed and therefore all the routing, the proxy is re
  05/13-17:24 . 4807  <pymjabdyi-qghxypl2e3y6.ml@delegate.org> [85]
___ On Thu, 13 May 2010 03:04:23 +0900 (JST), feedback@delegate.org (Yutaka to Yes - I'll include that - thanks. Ok, yes probably need that too. I assumed these flags had to be present on both sides of
  05/14-08:52 . 4808  feedback@delegate.org (Yutaka Sato) [32]
___ Hi, Hmm... it might be because you are using a kind of automatic proxy configuration (by .pac file) based on domain names or have a static exclusion list of destination hosts in your browser configu
  05/17-09:09 . 4809  feedback@delegate.org (Yutaka Sato) [33]
___ Hi, I found the reason. The HTTP proxy over yysh is implemented as multiple threads in a yysh server process. Each proxy thread was rejecting secondary requests over a connection in "keep-alive" wit
FTPxHTTP by DeleGate (Re: FTP to HTTP Protocol Translation Gateway)
  05/17-17:25 . 4810  feedback@delegate.org (Yutaka Sato) [114]
___ David, I've been interested in relaying FTP over HTTP (or HTTPS), or using a HTTP (HTTPS) server just to provide a file transfer service as a FTP server does. HTTP is a protocol that is easily route
  admin search upper oldest olders older1 this newer1 newers latest
[Top/Up] [oldest] - [Older+chunk] - [Newer+chunk] - [newest + Check]
Generated:05/23 04:39:39 (3 sec) Expires:05/23 10:39:36 @_@V