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

not able to fully pull content from WWW server

Nov 03 06 9:26 am

Hi,

Having a small issue with being able to retrieve served pages from the Wingate WWW service - kind of works but seems to get stuck - multiple click and/or page refresh usually gets the whole page loaded (I guess it slowly gets the whole page from the server into the local cache a few bits at a time...?) and is exactly the same whether I'm connecting locally or remotely

I have the served directories excluded from real time AV protection and the only rule configured for the service permits everyone if it is a non-proxy request, ignoring all other system settings and not making use of any plugins.

Please help me diagnose if you will here. (just some sample reports for testing)

Cheers :)
Last edited by willtech on Nov 03 06 11:52 am, edited 1 time in total.

Nov 03 06 11:45 am

I don't think it is a WG problem. I can't load that link correctly at the machine I'm at right now and it doesn't go through WG at all (just a router). Seems to be same issue you are describing - in fact I can't get it all to load at any time.

Nov 03 06 11:50 am

Hi ChrisH,

Maybe, but it was working for somebody about 10 minutes ago - that is, the Wingate WWW server was getting the requests at least.

Cheers :)
Last edited by willtech on Nov 03 06 3:06 pm, edited 1 time in total.

Nov 03 06 2:23 pm

Never finishes loading here - sans WinGate.

Nov 03 06 6:05 pm

labull wrote:Never finishes loading here - sans WinGate.
Yes indeed - that's the problem I'm talking about
Image

Nov 03 06 10:32 pm

Can you capture traffic to Wingate proxy for this website?

Nov 04 06 2:16 am

You mean packet capture for a session?
Or something else?

Also, I'm using http://www.wingate.com/downloads/drivers620.zip if it makes any difference

Cheers :)

EDIT: realised what you meant I think - I turned on debug now as well.
Code:
11/04/06 02:53:54   xxx.xxx.x.x   user01   0000007419   Created:   
11/04/06 02:53:54   xxx.xxx.x.x   user01   0000007419   Requested:   http: GET /
11/04/06 02:53:54   xxx.xxx.x.x   user01   0000007419   Debug:   [/] Copy to use: SERVER
11/04/06 02:53:54   xxx.xxx.x.x   user01   0000007419   Debug:   Served File D:/WWWroot/NOD32/ in thread a00
11/04/06 02:53:54   xxx.xxx.x.x   user01   0000007419   Traffic    10918   371   0   0   0s
11/04/06 02:53:54   xxx.xxx.x.x   user01   0000007420   Created:   
11/04/06 02:53:54   xxx.xxx.x.x   user01   0000007420   Requested:   http: GET /static_main.css
11/04/06 02:53:54   xxx.xxx.x.x   user01   0000007420   Debug:   [/static_main.css] Copy to use: SERVER
11/04/06 02:53:54   xxx.xxx.x.x   user01   0000007420   Debug:   Served File D:/WWWroot/NOD32/static_main.css in thread 85c
11/04/06 02:53:54   xxx.xxx.x.x   user01   0000007420   Traffic    1625   258   0   0   0s
11/04/06 02:53:54   xxx.xxx.x.x   user01   0000007421   Created:   
11/04/06 02:53:54   xxx.xxx.x.x   user01   0000007422   Created:   
11/04/06 02:53:54   xxx.xxx.x.x   user01   0000007423   Created:   
11/04/06 02:53:54   xxx.xxx.x.x   user01   0000007421   Requested:   http: GET /graph1tn_2.png
11/04/06 02:53:54   xxx.xxx.x.x   user01   0000007421   Debug:   [/graph1tn_2.png] Copy to use: SERVER
11/04/06 02:53:54   xxx.xxx.x.x   user01   0000007424   Created:   
11/04/06 02:53:54   xxx.xxx.x.x   user01   0000007421   Debug:   Served File D:/WWWroot/NOD32/graph1tn_2.png in thread d30
11/04/06 02:53:54   xxx.xxx.x.x   user01   0000007421   Traffic    9558   257   0   0   0s
11/04/06 02:53:54   xxx.xxx.x.x   user01   0000007425   Created:   
11/04/06 02:53:54   xxx.xxx.x.x   user01   0000007422   Requested:   http: GET /graph2tn_2.png
11/04/06 02:53:54   xxx.xxx.x.x   user01   0000007423   Requested:   http: GET /graph1tn_4.png
11/04/06 02:53:54   xxx.xxx.x.x   user01   0000007423   Debug:   [/graph1tn_4.png] Copy to use: SERVER
11/04/06 02:53:54   xxx.xxx.x.x   user01   0000007422   Debug:   [/graph2tn_2.png] Copy to use: SERVER
11/04/06 02:53:54   xxx.xxx.x.x   user01   0000007422   Debug:   Served File D:/WWWroot/NOD32/graph2tn_2.png in thread 7e8
11/04/06 02:53:54   xxx.xxx.x.x   user01   0000007422   Traffic    8709   257   0   0   0s
11/04/06 02:53:54   xxx.xxx.x.x   user01   0000007425   Requested:   http: GET /graph1tn_20.png
11/04/06 02:53:54   xxx.xxx.x.x   user01   0000007425   Debug:   [/graph1tn_20.png] Copy to use: SERVER
11/04/06 02:53:54   xxx.xxx.x.x   user01   0000007424   Requested:   http: GET /graph2tn_4.png
11/04/06 02:53:54   xxx.xxx.x.x   user01   0000007424   Debug:   [/graph2tn_4.png] Copy to use: SERVER
11/04/06 02:53:54   xxx.xxx.x.x   user01   0000007425   Debug:   Served File D:/WWWroot/NOD32/graph1tn_20.png in thread e7c
11/04/06 02:53:54   xxx.xxx.x.x   user01   0000007425   Traffic    11970   258   0   0   0s
11/04/06 02:53:54   xxx.xxx.x.x   user01   0000007423   Debug:   Served File D:/WWWroot/NOD32/graph1tn_4.png in thread b08
11/04/06 02:53:54   xxx.xxx.x.x   user01   0000007423   Traffic    26552   257   0   0   0s
11/04/06 02:53:54   xxx.xxx.x.x   user01   0000007424   Debug:   Served File D:/WWWroot/NOD32/graph2tn_4.png in thread b28
11/04/06 02:53:54   xxx.xxx.x.x   user01   0000007424   Traffic    33828   257   0   0   0s
11/04/06 02:53:55   192.168.1.5   damian   0000007426   Created:   
11/04/06 02:53:55   192.168.1.5   damian   0000007427   Created:   
11/04/06 02:53:55   192.168.1.5   damian   0000007427   Requested:   http: GET /graph3tn_20.png
11/04/06 02:53:55   192.168.1.5   damian   0000007427   Debug:   [/graph3tn_20.png] Copy to use: SERVER
11/04/06 02:53:55   192.168.1.5   damian   0000007426   Requested:   http: GET /graph2tn_20.png
11/04/06 02:53:55   192.168.1.5   damian   0000007426   Debug:   [/graph2tn_20.png] Copy to use: SERVER
11/04/06 02:53:55   192.168.1.5   damian   0000007428   Created:   
11/04/06 02:53:55   192.168.1.5   damian   0000007428   Requested:   http: GET /graph4tn_20.png
11/04/06 02:53:55   192.168.1.5   damian   0000007428   Debug:   [/graph4tn_20.png] Copy to use: SERVER
11/04/06 02:53:55   192.168.1.5   damian   0000007427   Debug:   Served File D:/WWWroot/NOD32/graph3tn_20.png in thread 9dc
11/04/06 02:53:55   192.168.1.5   damian   0000007427   Traffic    11276   258   0   0   0s
11/04/06 02:53:55   192.168.1.5   damian   0000007426   Debug:   Served File D:/WWWroot/NOD32/graph2tn_20.png in thread d24
11/04/06 02:53:55   192.168.1.5   damian   0000007426   Traffic    11369   258   0   0   0s
11/04/06 02:53:55   192.168.1.5   damian   0000007428   Debug:   Served File D:/WWWroot/NOD32/graph4tn_20.png in thread a98
11/04/06 02:53:55   192.168.1.5   damian   0000007428   Traffic    11117   258   0

Nov 06 06 8:12 am

Just to compare with only the server different,
This is the same link I first posted on my Wingate http://snipurl.com/112oc-report
This is another ISP hosted location http://snipurl.com/11ac3

Notice the second one works well...

Really need to get this issue sorted. My Wingate is running on a Dual P3 box with 512MB RAM and XP Pro SP1 with all current M$ patches that SP1 will accept and the patched wingate drivers from elsewhere in this forum. It makes no difference if I connect from the LAN or the Internet.

Does the traffic log reveal anything?

Cheers :)

Nov 06 06 11:18 am

willtech wrote:Just to compare with only the server different,
This is the same link I first posted on my Wingate http://snipurl.com/112oc-report
This is another ISP hosted location http://snipurl.com/11ac3

Notice the second one works well...


Hi,

Not using Wingate at all it doesn't completely load.

On a client machine using proxies it does complete for me using SeaMonkey 1.1a, but it took maybe a minute longer than ii.

Also URL i uses a non standard port :88 which is odd but shouldn't matter I guess.

Nov 06 06 11:31 am

Apprecite you checking it - confirms it's not just an issue with the PCs I've been trying to connect to it with.

So what do you suggest? Does the 'Squid Compliant' checkbox indicate that the wingate service runs as a squid compliant service or the the ISP is a squid compliant service provider and could that make a difference? (doesn't seem to - is a reboot required for it to take effect?

Cheers :)

Nov 06 06 12:22 pm

genie wrote:Can you capture traffic to Wingate proxy for this website?
This website is being served by the wingate.

Nov 06 06 9:54 pm

Hi

We're looking into this.

In the mean time, you probably need to add a couple of mime types to WinGate's WWW proxy.

these live in HKLM\Software\Qbik Software\WinGate\MimeTypes

You'll need to add

string value called "css", content "text/css"
string value called "png" content "image/png"

This will make WinGate serve the correct mime types for these files.

We've repro'd the issue in the lab here as well and we're chasing a couple of other issues.

Adrien

Nov 07 06 4:06 am

Thanks - added those.
Is a service bounce required?

edit: ...nevermind, it just had one anyway :)

Nov 09 06 12:07 pm

Have a workaround for this issue tested and working (i think) that I'll put in place later on after confirming.

EDIT: Nevermind, ultimately it made no difference.

Cheers :)

Nov 09 06 1:50 pm

There is also an issue with 6.1.4 using WinGate's WWW service and CGI POSTs.

I bellieve James has your setup here in the lab, so we should be able to debug and make sure the next release works for you. It's due out quite soon.

Adrien

Nov 09 06 2:07 pm

adrien wrote:There is also an issue with 6.1.4 using WinGate's WWW service and CGI POSTs.

I bellieve James has your setup here in the lab, so we should be able to debug and make sure the next release works for you. It's due out quite soon.

Adrien
OK Adrien, I'll wait patiently :)

Jan 07 07 6:01 pm

Can anybody confirm if this issue will be resolved by upgrading to SP2?
Or is it a multiprocessor issue?
Or just simple Wingate issue?

Cheers :)

Jan 17 07 2:11 pm

Hi

We're doing a bit of major work to the WWW proxy at the moment. If you'd like to test it would be really appreciated, it addresses issues of POST requests through proxy to server each/either requiring NTLM etc, pipelining of requests, support for connection keepalives etc.

As for the Squid compliant thing. All that does is append a header to any upstream request ("X-Forwarded-For: xx.xx.xx.xx") with the IP of the client behind WinGate. This is done for upstream squid proxies to improve caching.

Adrien
Post a reply