On 07.05.21 06:52, Aniruddha Gore wrote:
Thanks Matus for responding 🙂
no need for private copy, mailing list is enough.
Following is what the relevant line in squid.conf:
# Squid normally listens to port 3128
http_port 3128
I suspect you might be pointing out that there is no https_port configured.
no. https_port is used for reverse proxying, not for forward proxying of
HTTPS requests.
While I was adding https_port, I noticed no process is listening on port
3128 (doesn't appear in output of netstat -aon on Windows). So now the
calls are failing with "WinHttpSendRequest: 12029: A connection with the
server could not be established" 😕
have you set up your squid host:port as HTTP proxy in the application?
- means: have you set up the applictaion to use HTTP proxy?
Can you see anything in squid logs?
- what is in squid logs?
From: squid-users <squid-users-bounces@xxxxxxxxxxxxxxxxxxxxx> on behalf of Matus UHLAR - fantomas <uhlar@xxxxxxxxxxx>
On 06.05.21 01:06, Aniruddha Gore wrote:
Pinging back hoping to get some help. I suspect I am missing something
very basic and would really appreciate if someone could point me in the
right direction. :)
I haven't seen your packet trace but so far it shouldn't be needed.
Context I have an application running on a machine (A) that does not have
internet connectivity. It, however, can talk to another machine (B) which
has full connectivity. The application makes HTTPS calls. I am hoping to
set-up Squid on B and set-up web proxy (ip address and port) when making
HTTPS calls in the app.
I have installed Squid for
Windows<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsquid.diladele.com%2F&data=04%7C01%7C%7Ceb0f33fc98ae42629d1e08d91055edbb%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637558783534261214%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=iT5UB59%2BSbNulVVbsgRSh81lxp0lMkSeBv%2Fmj5y1CVE%3D&reserved=0>
on B with default squid config.
Problem HTTPS requests are timing out.
I am new to proxy so don't know lot of ways to investigate further. This
is what Wireshark captured running on B. Unfortunately, I am unable to
gather any actionable info from this, it just confirms that calls do make
it to B and then something wrong happens.
--
Matus UHLAR - fantomas, uhlar@xxxxxxxxxxx ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
Spam = (S)tupid (P)eople's (A)dvertising (M)ethod
_______________________________________________
squid-users mailing list
squid-users@xxxxxxxxxxxxxxxxxxxxx
http://lists.squid-cache.org/listinfo/squid-users
