Switch to full style
Use this forum to post questions relating to WinGate, feature requests, technical or configuration problems
Post a reply

File download issue

Apr 25 05 8:14 pm

I got a small but disappointed problem with WG 6.0.4.
When i start downloading a file thru WG my download manager show me that "resume download" is not supported.
Without WG everything seems to be ok.
So, what i must tune in WWW proxy service to support resuming and multi thread download too?

Apr 25 05 8:23 pm

Try using the FTP proxy. Ensure that "block FTP restart" is not ticked on it's general page.

uhm...

Apr 25 05 9:06 pm

However, what if my link looks like "www.something.com/files/file.zip".
How can I use ftp proxy in this case?

Apr 25 05 9:34 pm

Do you have a sample link + name of download manager so I can try it tomorrow?

ok

Apr 26 05 1:23 am

Ok. http://www.lysator.liu.se/~zap/revelations/revelations_film_QT_large.mov
Download manager: ReGet Deluxe 4.1
File is 250 Mb long, so it's very critical to have resuming capabilities for files like this.

Apr 26 05 8:13 am

Are you using any data-scanning plugins? If they are in use the HTTP 1.1 "range" tag is disabled. (Which, I assume, is how ReGet would do it, by requesting a different range)

Apr 26 05 6:19 pm

Pascal wrote:Are you using any data-scanning plugins?


Only Puresight.

If they are in use the HTTP 1.1 "range" tag is disabled. (Which, I
assume, is how ReGet would do it, by requesting a different range)


Uhm... i must disable puresight and try again?

Apr 26 05 6:30 pm

Easiest option might be to create a secondary proxy which does not use PureSight and try that, yeah. According to the source code we disable the range command. Which makes sense, because using range you can download a virus in increments with the scanners being unable to pick up on it.

:(

Apr 27 05 1:27 am

Pascal wrote:Easiest option might be to create a secondary proxy which does not use PureSight and try that, yeah. According to the source code we disable the range command. Which makes sense, because using range you can download a virus in increments with the scanners being unable to pick up on it.


I created another WWW proxy service on another port. Puresight was disabled in it. Still no luck. :( No resuming or multi-thread dowload.
Any clue?

Apr 27 05 8:09 am

That was the only tag I could discover in the HTTP 1.1 RFC that would allow resuming of a download and that is disabled if there are any enabled Plugins for that service.

I'll flip this one on to QA.

Apr 27 05 4:39 pm

Hi there

Just ran this through the lab here today but unfortunately wasnt able to replicate the issue. Used the latest downloadable version of Reget and Puresite installed but disabled WinGate.

What method is your clients connecting through WinGate (NAT,WGIC, or setting the Proxy in Reget)

I tried both a NAT (redirected through WWW proxy in WinGate) and using the Proxy connection setting in Reget to the link you gave, but had success both times so I couldnt replicate it.

If you can give anymore details on your setup (type of client connection, the Internet connection etc) then we could hopefully isolate it a bit more.

Regards
Erwin

:|

Apr 27 05 8:09 pm

Okay. I have a LAN with a more than 30 users. This users connecting to Windows 2000 Server (not advanced server) machine with SP4 installed.
Server has a WG 6.0.4 with Puresight 1.1. and a two network cards (into LAN and into Internet). Internet coming from fibre channel converter.
Users have an IE 5.0 or 6.0 installed and ReGet Deluxe 4.1 (build 241).
Connection properties in IE are: [internal address]:port 8010
"One address for all protocols" checked as "on".
WWW proxy service have puresight filter enabled and SSL:443 allowed.
No Java or WGIC auth.
Settings in ReGet: Preferences -> Proxy:
Type HTTP proxy: HTTP
Server name: [internal address]:8010
:)

Apr 27 05 8:17 pm

One other thing - what http protocol version were they showing in ReGet?

:|

Apr 27 05 11:32 pm

Pascal wrote:One other thing - what http protocol version were they showing in ReGet?


In a default properties for HTTP i see "use HTTP 1.1" setting.
This setting is _unchecked_. So... 1.0 using by default as i think.

Apr 28 05 9:13 am

Ok, that is what we were seeing as well. Erwin has some other ideas.

:|

Apr 28 05 6:38 pm

Okay. I'll wait.
Thank you for patience. :)

Apr 29 05 10:21 am

Hi there Surfer

After following your setup again I was able to replicate the issue BUT only with the Puresight plugin enabled on the 2nd WWW proxy service that I was using (using HTTP 1.1 set in Reget).

This is to be expected since as Pascal mentioned earlier:

That was the only tag I could discover in the HTTP 1.1 RFC that would allow resuming of a download and that is disabled if there are any enabled Plugins for that service.


This is done as a safeguard top prevent any viruses etc coming through the service(via retries) which is why you get the message in Reget that the server doesn't support retries.

So as a workaround you could create a second WWW service in WinGate purely for Reget clients to connect to. Disable the plugin for this particular service and have your clients set there Reget program to use this for downloading via HTTP. Obviously there will be no protection from plugins for the Reget users.

Also I noticed that you configured your WWW service for port 8010 which is the default port for the Logfile Service in WinGate, I presume that you have deleted/dont require the Logfile service for this to work that way.

Regards
Erwin

:)

Apr 29 05 6:31 pm

erwin wrote:Hi there Surfer
So as a workaround you could create a second WWW service in WinGate purely for Reget clients to connect to. Disable the plugin for this particular service and have your clients set there Reget program to use this for downloading via HTTP. Obviously there will be no protection from plugins for the Reget users.


Yes, it works. Thank you. Must be a good idea to incude this into help files.

Also I noticed that you configured your WWW service for port 8010 which is the default port for the Logfile Service in WinGate, I presume that you have deleted/dont require the Logfile service for this to work that way.


I migrate Logfile service to 8020. It's our local trick. :)
Post a reply