ASP.NET Web Clipping Control(repost)(repost)

Greetings, We would like to build an ASP.NET control (or code) that is used to scrap content from the given URL, apply transformations and render the result in the given container. In Java portal world the principle is also known as Web Clipping or WebConnector. When hosted on an ASP.NET page and surrounded by other content and controls this control would perform as if it was an iframe of the provided source address, however no iframe should be in sight - the content should be proxied by the component and rendered with the transformations defined below. ## Deliverables Greetings, We would like to build an ASP.NET control (or code) that is used to scrap content from the given URL, apply transformations and render the output in the given container. In the Java portal world the principle is also known as Web Clipping or WebConnector. When hosted on an ASP.NET page and surrounded by other content and controls this control would perform as if it was an iframe of the provided source address, however no iframe should be in sight - the content should be proxied by the component and rendered with the transformations defined below. The examples could be consulted at: <[login to view URL]> <[login to view URL]> The only technical problem previewed is JavaScript isolation and handling. The implementation should include basic JavaScript parsing and correct remapping of popup windows/ajax calls to the source host. A bonus will be offered if the deliverables shall handle JavaScript in a more advanced manner. Some of the Java portals we examined use HtmlUnit to act as a true web browser behind the scenes which is terribly slow when javascript is on. The only existing alternative of HtmlUnit that we've found is xbrowser which we have not tested because of the lack of JavaScript support. Requirements summary: Design - ASP.NET server control or a stand-alone class with its own state management - Custom state management - error, authentication error, protocol error HTML templates Protocol (HttpWebRequest tuning) - Support of URL-based clipping (i.e. http/https, any port, any valid URL) - proxy support - Redirection following and status code conditions, i.e. proxy 301 redirects but follow 404 errors - basic/windows authentication - custom authentication based on form elements (URL, username parameter, password parameter, request method, expected response, failure response) - Cookie persistence, cookie proxification (i.e. cookies inherited from the hosting website are transformed and passed to the proxied website) - Custom HTTP header submission, reception - Proxied / passed-thru, excluded content types/extensions/regex patterns Content Parser - chained filters that extract or remove the content (i.e. remove google analytics tags) - Tidy processor - XSLT template - DOM path - XPath path - Byte range - Pattern from/to - comment/element Attached file contains screenshots of a uPortal configurator that will help to understand the settings and approximate configuration settings of the new component. We would like to be actively participating in the component development, provide test cases, clarify the requirements and similar and are expecting updates of deliverables as frequently as possible (2-3 day intervals are ideal). The code must follow the naming conventions that will be provided. We do not expect a throughout documentation of the deliverable but comments on crucial parts are a must. The communication language is English. Should you need more information or precisions regarding the bid please feel free to post the questions here. When replying with a price please estimate the implementation time for the items of requirements summary above and justify the bid amount. Thank you for your attention and happy bidding! ## Platform Windows Server Family (2003+), ASP.NET, .NET Framework 3.5