This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Problem with ASL5-HTTP-Proxy running on Port 3128

On my ASL5 I had to change the HTTP proxy-port from 8080 to 3128.

Access to some redirected web-sites does not work properly with port 3128. With Proxy on port 8080 it works fine. The proxy also worked fine with ASL4 on both ports.

Example to reproduce the error: Got to www.avm.de, try to download some driver. You will see the error after selection of product and operating system and just pressing the button to proceed...

Proxy is in standard mode, no authetication, clients use IE6.

regards
Thilo.li

This thread was automatically locked due to age.

Parents

0 Snova over 21 years ago

You have to add port 8080 to the allowed services. In V4 you did that in moving the service "squid" to the allowed services window. This should work whatever port you use on the internal network.

Jan
Cancel
Vote Up 0 Vote Down

Cancel
0 thilo over 21 years ago in reply to Snova

Hi Jan,

I had already added "SQUID" to the list of allowed services ;-( This seems not to solve the problem.

Thilo
Cancel
Vote Up 0 Vote Down

Cancel
0 Marcel_01 over 21 years ago in reply to thilo

confirmed - this is a bug... as a workaround, add a new service definition with port 8080 and add it to the allowed target services

~marcel
Cancel
Vote Up 0 Vote Down

Cancel
0 thilo over 21 years ago in reply to Marcel_01

A Service with Port 8080 is already there.

It seems to be a problem with the automatic generation of packet-filter rules. When the error occurs, you can see some new entries in the packet-filter live log.
Cancel
Vote Up 0 Vote Down

Cancel
0 skaiser over 21 years ago in reply to thilo

Hmm,

I have also running the Proxy on Port 3128 and most things work fine. I have also enabled the virus protection and there was a bug with showing xml-content right? This was fixed in an up2date package. But there is a Problem with Web-Downloads linked to ftp-sites.
There is still xml displayed:

-
-
TcpSocket.cpp:119:connect:TCP Connect failed to 127.0.0.1:8080 (127.0.0.1)
Cancel
Vote Up 0 Vote Down

Cancel
0 Vukasin over 21 years ago in reply to skaiser

the scanner uses the squid to fetch the ftp content. the problem is that it always uses 127.0.0.1:8080 so the workaround for this would be to have a DNAT 127.0.0.1:8080->127.0.0.1:YOURPORT
Cancel
Vote Up 0 Vote Down

Cancel
0 skaiser over 21 years ago in reply to Vukasin

Hi,

I have changed the Proxy-Port back to 8080, and the error message has gone, but the xml content is still displayed.

Stefan
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 skaiser over 21 years ago in reply to Vukasin

Hi,

I have changed the Proxy-Port back to 8080, and the error message has gone, but the xml content is still displayed.

Stefan
Cancel
Vote Up 0 Vote Down

Cancel

Children

0 skaiser over 21 years ago in reply to skaiser

Maybe I have found something usefull:

If I start a download, and the xml content is displayed, I push the IE Reload-Button two times, then the "normal" Astaro Download screen is showing.
The only problem still active is the incorrect file size, eg 338 Kb.

Stefan
Cancel
Vote Up 0 Vote Down

Cancel