it seems like a dns problem.
this domain :ameymdm.ameygroup.int
is an internal one so squid should have access to this dns record.
you can try another solution by using exceptions in iptables for inside
ip's servers.
Eliezer
On 24/05/2012 16:11, Fosiul Alam wrote:
Hi
i am facing a wired behaviour from squid.
we are trying to connect to via Jupiter windows secure application
manager to a clients network via http( Soti Mobi Control)
its works fine from outside of our network , even though from same
internal network without squid proxy .. but when it try to go via
squid, it does not able to resolve the address!!!
example :
after typing username and password , its goes to here
https://portal.amey.co.uk/dana/home/launch.cgi?url=https%3A%2F%2Fameymdm.ameygroup.int%2Fmobicontrol%2F
and it suppose to through a Certificate Error and from their it should go to
https://ameymdm.ameygroup.int/mobicontrol/
but it does not through any Certificate error not it goes to
https://ameymdm.ameygroup.int/mobicontrol/
instead of that its say :
The webpage cannot be found
i think its something to do with "https%3A%2F%2Fameymdm" which squid
does not know how to parse.. there is not any deny in squid log.
the log i get :
1337864980.578 33479 192.0.0.131 TCP_MISS/200 24512 CONNECT
portal.amey.co.uk:443 - DIRECT/216.31.202.163 -
1337865025.716 0 192.0.0.131 TCP_MISS/404 0 CONNECT
ameymdm.ameygroup.int:443 - DIRECT/- -
Can any one help me to find out what happenning ...
As i said, if i try without proxy, it works fine. but with proxy it does not ..
Regards
--
Eliezer Croitoru
https://www1.ngtech.co.il
IT consulting for Nonprofit organizations
eliezer <at> ngtech.co.il
