大网数据广告活动
服务器运维问答

Is it common for HTTP proxy to connect to ANY destination port indicated in HTTP request?

· 52CE 我爱测

Is it common for HTTP proxy to connect to ANY destination port indicated in HTTP request? Or usually set of destination ports is restricted (80, 8080, 443, ...) I created WCF service and Visual Studio assigned address http://loca…

问题原文

原帖链接 · Vlad · CC BY-SA 3.0

Is it common for HTTP proxy to connect to ANY destination port indicated in HTTP request? Or usually set of destination ports is restricted (80, 8080, 443, ...) I created WCF service and Visual Studio assigned address http://localhost:7517/ But some customers can use web proxies and it seems that using standard 80 or 8080 is good idea for WCF service, doesn't it? Otherwise what is the benefit HTTP based WCF VS TCP based WCF... From other side 80 or 8080 can be occupied already. What are the most common proxy destination port restrictions nowadays? This information is useful for setting WCF HTTP transport based service port.

已采纳解答

原帖链接 · Tom Newton · CC BY-SA 3.0

Yes, this is very often restricted. Particularly any proxy based on squid, as this functionality is standard. Also it is a line of defence against people tunneling through proxies.

Squid standard config has

acl Safe_ports port 80 21 443 563 70 210 1025-65535 http_access deny 

Many people knock off the high ports, too.

My advice is to try and stick to 80 and 443 where possible for Web services, outside that it can be hard to predict which proxies will block. If you are serving a market such as education where filters or proxies are almost ubiquitous, it's definitely worth playing safe.

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Server Fault
适用范围
以原帖系统、软件版本与发布日期为准(2016-03-30)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 3.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。