Upstream hardware proxy help

[Nev]

Hi all,

This one has baffled me so am calling for help.

Hardware is a private range NAT IP device to the internet.

Normal TCP/IP ports are handled by it without difficulty, however to overcome [satellite] path latency it has an inbuilt WWW proxy/port without support for SSL.

Configuring [as required ie: gateway and port 9877] directly to it gives a very noticeable page load improvement on the server, however it is stated the proxy does not support SSL, which must remain NAT or directly connected.

Cascading the WWW service in Wingate to the respective IP/Port in the device gives the same performance to all clients and localhost requests.

Until, an SSL event is requested, all browsing stops completely after the login succeeds.

Have tried alternate Port mappings & cascading without plugins, nil policies, nil firewall hits at any time!

Second part of my question is, would NAT utilise this proxy say with a redirect to the IP/Port? I guess not?

Below is a log extract of enhanced surfing then SSL and session failure for all.

Requested: http://abc.net.au/img3/gn02links.gif
Debug: WWW Session sending server request in thread 574
Requested: http://www.abc.net.au/triplej/navigation/img/logo.gif
Debug: WWW Session sending server request in thread 61c
Debug: Server response contains 228 bytes of resource data
Debug: WWW Session processing HTTP response in thread 21c - response code 200
Traffic 477 572 535 477 0s
Requested: http://abc.net.au/triplej/img/triplej_banner_top.gif
Debug: WWW Session sending server request in thread 21c
Debug: Server response contains 427 bytes of resource data
Debug: WWW Session processing HTTP response in thread 574 - response code 200
Debug: Server response contains 894 bytes of resource data
Debug: Server response contains 1010 bytes of resource data
Debug: WWW Session processing HTTP response in thread 61c - response code 200
Debug: WWW Session processing HTTP response in thread 21c - response code 200
Traffic 677 559 522 677 0s
Traffic 1261 575 538 1261 0s
Traffic 1144 580 543 1144 0s
Requested: http://abc.net.au/triplej/review/img/fi ... r_main.gif
Debug: WWW Session sending server request in thread 574
Requested: http://www.abc.net.au/triplej/img/chat_icon.gif
Requested: http://abc.net.au/triplej/img/listen_icon.gif
Debug: WWW Session sending server request in thread 21c
Debug: WWW Session sending server request in thread 61c
Debug: Server response contains 1042 bytes of resource data
Debug: WWW Session processing HTTP response in thread 574 - response code 200
Debug: Server response contains 173 bytes of resource data
Debug: Server response contains 167 bytes of resource data
Debug: WWW Session processing HTTP response in thread 21c - response code 200
Debug: WWW Session processing HTTP response in thread 61c - response code 200
Traffic 5055 588 551 5055 0s
Traffic 416 567 530 416 0s
Traffic 421 572 535 421 0s
Requested: http://abc.net.au/triplej/img/line_515.gif
Requested: http://www.abc.net.au/triplej/img/house_icon.gif
Requested: http://abc.net.au/triplej/review/img/ti ... e_film.gif
Debug: WWW Session sending server request in thread 61c
Debug: WWW Session sending server request in thread 574
Debug: WWW Session sending server request in thread 21c
Debug: Server response contains 185 bytes of resource data
Debug: WWW Session processing HTTP response in thread 61c - response code 200
Traffic 434 564 527 434 0s
Requested: http://www.abc.net.au/triplej/highlight ... rdream.gif
Debug: Server response contains 168 bytes of resource data
Debug: WWW Session processing HTTP response in thread 574 - response code 200
Debug: Server response contains 1328 bytes of resource data
Debug: WWW Session sending server request in thread 61c
Debug: WWW Session processing HTTP response in thread 21c - response code 200
Traffic 1579 590 553 1579 0s
Traffic 417 574 537 417 0s
Requested: http://www.abc.net.au/triplej/highlight ... ntjaxx.gif
Requested: http://www.abc.net.au/triplej/highlight ... _award.gif
Debug: WWW Session sending server request in thread 574
Debug: WWW Session sending server request in thread 21c
Debug: Server response contains 3350 bytes of resource data
Debug: WWW Session processing HTTP response in thread 61c - response code 200
Debug: Server response contains 1042 bytes of resource data
Debug: WWW Session processing HTTP response in thread 21c - response code 200
Traffic 3601 592 555 3601 1s
Debug: Server response contains 1043 bytes of resource data
Debug: WWW Session processing HTTP response in thread 574 - response code 200
Requested: http://abc.net.au/triplej/img/bg.gif
Traffic 7071 589 552 7071 1s
Traffic 2744 583 546 2744 1s
Debug: WWW Session sending server request in thread 61c
Debug: WWW Session processing HTTP response in thread 61c - response code 304
Traffic 123 607 570 131 1s
Debug: Server closed connection in thread 61c
Traffic 0 0 0 0 0s
Terminated exit code 0
Debug: More to come in server response server response 200
Debug: Server response contains 1147 bytes of resource data
Debug: WWW Session processing HTTP response in thread 508 - response code 200
Debug: Cookie set in server response - disabling caching
Requested: http://au.f522.mail.yahoo.com/favicon.ico
Debug: WWW Session sending server request in thread 21c
Requested: http://us.js1.yimg.com/us.yimg.com/lib/ ... mmonlib.js
Debug: WWW Session sending cached resource to client in thread 574
Debug: Sent Cached Resource us.js1.yimg.com/us.yimg.com/lib/pim/r/medici/9_11/mail/mailcommonlib.js in thread 574
Traffic 24136 457 0 0 2s
Debug: Server closed connection in thread 508
Traffic 5297 940 903 5272 3s
Terminated exit code 0
Created:
Requested: http://au.f522.mail.yahoo.com/ym/welcome
Debug: WWW Session sending server request in thread 574
Requested: http://au.f522.mail.yahoo.com/ym/instacompose
Debug: WWW Session sending server request in thread 61c
Debug: Client closed connection in thread 21c
Traffic 0 1996 1959 0 16s
Terminated exit code 1
Traffic 0 2175 2138 0 16s
Terminated exit code 2
Traffic 0 2176 2139 0 16s
Terminated exit code 2
Created:
Requested: http://au.f522.mail.yahoo.com/ym/welcome
Debug: WWW Session sending server request in thread 21c
Created:
Requested: http://au.f522.mail.yahoo.com/favicon.ico
Debug: WWW Session sending server request in thread 61c
Created:
Requested: http://abc.net.au/triplej/review/film/f ... 2004_M.htm
Debug: WWW Session sending server request in thread 574
Traffic 0 2175 2138 0 16s
Terminated exit code 2
Traffic 0 1996 1959 0 16s
Terminated exit code 2
Traffic 0 598 561 0 16s
Terminated exit code 2

[Nev]

Hi all,

As previous, this works like a charm on the server but not for clients, the service is quite dull actually.

Any ideas / workarounds, appreciated.

[Nev]

Hi all,

Have given this one away, cannot make it work.

What seems to happen is the login succeeds but the session / user is not recognised once traffic is handed to the alternate proxy.

In any event it's only WWW traffic, all services are normal NAT by the device [including WWW] so have abandoned trying to make it work via Wingate.