拦截源自网页的每个请求-Intercepteveryrequestoriginatingfromawebpage

7  

In a word, no. There's no place you can hook into to get all the requests.

总之,没有。没有地方可以挂钩来获取所有请求。

Having said that, you can us Javascript to place event handlers on the links, look at the src attribute of image tags and so on. There's no "generic" way to hook into all the AJAX requests - it depends on the library you're using.

话虽如此,你可以使用Javascript在链接上放置事件处理程序,查看图像标记的src属性等等。没有“通用”方法来挂钩所有AJAX请求 - 它取决于您正在使用的库。

There are other things to consider, such as CSS background images, Flash (what if a flash file makes a request?).

还有其他需要考虑的事情,比如CSS背景图片,Flash(如果flash文件发出请求会怎样?)。

If possible you should be using the browser itself (e.g. Firebug) or a proxy (e.g. Fiddler) or a packet sniffer (e.g. Ethereal... seems to be WireShark now)

如果可能的话,你应该使用浏览器本身(例如Firebug)或代理(例如Fiddler)或数据包嗅探器(例如Ethereal ......现在似乎是WireShark)

0  

Greg's right, there's no one place you can hook into all the requests. Having said that, what is your end goal in rewriting all the requests? If you need to add a "parameter" to every request and then use it on the server side, one way to do it is the host header. You can modify the host header on the server side (i.e. redirect the user from your-site.com to your-parameter.your-site.com) and all the requests after that will have *your-parameter" in it. On the server-side, you can use url-rewriting techniques to modify the url to your-site.com?parameter=your-parameter.

格雷格是对的,没有一个地方可以挂钩所有请求。话虽如此,重写所有请求的最终目标是什么?如果您需要为每个请求添加“参数”,然后在服务器端使用它,那么一种方法是主机头。您可以修改服务器端的主机头(即将用户从your-site.com重定向到your-parameter.your-site.com),之后的所有请求都将包含* your-parameter“。在服务器端,您可以使用网址重写技术将网址修改为your-site.com?parameter=your-parameter。

For redirecting use the http 302 response code. Appropriate url-rewriting component will need to be set up on the server-side (mod_rewrite for apache, ISAPIrewrite for ASP.NET)

对于重定向使用http 302响应代码。需要在服务器端设置适当的url-rewriting组件(mod_rewrite用于apache,ISAPIrewrite用于ASP.NET)

Some points to noted: 1) The user will not be logged out since the sub-domains and domains share the session COOKIE 2) You will need to set up wildcard mapping on your DNS server 3) The browser caching will not be as effective 4) You need to analyze the "business-impact" of a changed url

需要注意的一些要点:1)由于子域和域共享会话COOKIE,用户将不会被注销2)您需要在DNS服务器上设置通配符映射3)浏览器缓存不会有效4 )您需要分析更改的网址的“业务影响”