When a user or an application browses through the proxy and they find that they can't access a website, the first question that arises is whether it's due to the proxy service or it's environment.
Indeed, the proxy may be blocked by the firewall, lack access to DNS, or have insufficient network routing to reach the request.This feature is available on Artica v4.50 Service Pack 1 or Artica v4.50 Hotfix 20240914-17
Before blaming the proxy's functionality or the filtering rules/ACLs that have been implemented, it is necessary to have definite proof that the physical path to the website is correctly evaluated.
Artica provides a feature that allows you to assess this type of situation.
To help you identify the access error, an analysis tool is available in the real-time Internet access viewer.
Using the REST API, simply use:
GET http://1.2.3.4:9503/analyze/website/direct/[domain]
Where domain can be a full hostname ( id.google.com ) or the full hostname and the port ( id.google.com:443)
The query will return a json that provide all tests results:
Example of the query http://1.2.3.4:9503/analyze/website/direct/id.google.com:443
{ "domain_test": true, "domain_record": "216.58.200.3", "telnet": true, "telnet_error": "", "proto": "https", "port": 443, "domain": "id.google.com", "query_url": "https://id.google.com:443/", "direct_http": true, "direct_http_error": "", "direct_http_err_code": 404, "direct_http_response_headers": [ "Alt-Svc: h3=\":443\"; ma=2592000,h3-29=\":443\"; ma=2592000", "Date: Sat, 14 Sep 2024 16:07:42 GMT", "Content-Type: text/html; charset=UTF-8", "Server: scaffolding on HTTPServer2", "Content-Length: 1561", "X-Xss-Protection: 0", "X-Frame-Options: SAMEORIGIN" ], "proxy_enable": true, "proxy_url": "http://127.0.0.1:62396", "proxy_error": false, "proxy_error_str": "", "proxy_response_headers": [ "Date: Sat, 14 Sep 2024 16:07:42 GMT", "Content-Type: text/html; charset=UTF-8", "Server: scaffolding on HTTPServer2", "Content-Length: 1561", "X-Xss-Protection: 0", "X-Frame-Options: SAMEORIGIN", "Alt-Svc: h3=\":443\"; ma=2592000,h3-29=\":443\"; ma=2592000" ], "proxy_response_code": 404, "proxy_dns": [ { "dnsname": "192.168.1.20", "dns_success": true, "dns_error": "", "dns_result": "142.250.178.131, 2a00:1450:4019:80b::2003" }, { "dnsname": "1.1.1.1", "dns_success": true, "dns_error": "", "dns_result": "172.217.18.195, 2607:f8b0:4002:c02::5e" } ]}