C# WebBrowser 或普通浏览器
我从论坛网站收到“禁止”消息，原因是我的 Windows 应用程序尝试通过以下代码通过网络浏览器控制进行连接：
webbrowser1.Navigate("http://www.xyz.com");
我可以使用我的普通浏览器（IE8.0 和 FireFox 3.6）进行连接，而不会出现任何“禁止”消息。我找不到我的应用程序和普通浏览器之间的任何差异。看来“禁止”消息与我的 IP 地址、cookie 或标头信息（用户代理、HTTP 接受）无关
请帮忙：这个论坛网站如何实现我来自普通浏览器或应用程序的请求？
注意：抱歉我的英语不好。感谢您的理解。
I'm getting "banned" message from a forum site cause of my windows application which tries to connect over webbrowser control by this code:
webbrowser1.Navigate("http://www.xyz.com");
I can connect without any "banned" message with my normal browsers both IE8.0 and FireFox 3.6. I cannot find any differences between my application and normal browser. It seems "banned" message is not related my IP address, cookies or header info (User-Agent, HTTP-Accept)
Please help: How can this forum site realize my request coming from normal browser or application?
Note: Sorry for my English. Thank you for your understanding.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
最基本的是，您仅发送以下信息：
上述其中一项必须存在差异，网站才能区分浏览器控件和您的实际情况浏览器 - 除非涉及多个请求，否则根本没有其他区别。
At its most basic you're only sending the following information:
There must be a difference in one of the above for the site to be able to differentiate between the browser control and your actual browser - There's simply no other difference unless multiple requests are involved.
我认为他们禁止的IP是您的系统IP而不是您的连接IP，可以更改但系统IP不能。
某些应用程序将其代理设置为 Firefox 的用户代理，然后服务器无法发现请求不是来自他们发出的浏览器，因为他们需要服务器无法找到通过代码而不仅仅是使用浏览器访问其网站的人。
我的答案与你的问题没有任何匹配。
虚假身份意味着我讲述应用程序内的代码发出的请求，而不是浏览器用户使用的请求。
用户代理的更改使它们成为正常请求，它们无法找到通过代码而不是浏览器发出的请求。
I thing they banned the IP is your system IP not your connection IP who can be change but system IP can not.
some application set their agent like Firefox's user agent then server can't find that the request not come from browser they make them because they need that server can't find somebody going of their site by code not just using browser.
the answer i put nothing match to your question.
Fake identity means i tell about the request make by code inside a application not by browser user use.
the user-agent change make them as normal request that they can't find the request they have come by code not by browser.