I assume you mean resources linked to via the likes of <img href="Image1.jpg">. Those "links" are retrieved as separate HTTP requests; and whenever the browser feels like it. There's no guarantee they'll be requested adjacent to the original page's request either.
If you want to find out what dependant files page1.aspx links to you'll have to parse the HTML returned from page1.aspx looking for "link" elements like IMG or LINK. Why do you need to do this? I ask because it influences how you would go about achieving this. On Wed, 8 Mar 2006 14:36:46 +0000, Paul Cowan <[EMAIL PROTECTED]> wrote: >Hi all, > >Can anyone help me with the following requirements? We want to parse an >HTTP request for a web page and display all the constituent parts that make >up the web page. That is I want to display all the additional requests that >are made to make up the whole page (i.e. css, images and javascript files). >Say I make a request for page1.aspx then the system would log that it is >made up of the following resources: > >Default.css >Modern.css >Image1.jpg >Script.js >Etc., etc. > >I have no idea how to achieve this, does anybody know?? =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
