http://blog.httpwatch.com/2007/11/20/error_internet_invalid_url-httpwatch/#utm_source=rss&utm_medium=rss&utm_campaign=error_internet_invalid_url-httpwatch News, articles and all things HttpWatch Fri, 03 Feb 2012 21:31:46 +0000 hourly 1 http://wordpress.org/?v=3.3.1 http://blog.httpwatch.com/2007/11/20/error_internet_invalid_url-httpwatch/comment-page-1/#comment-64870 dingjsh Sun, 29 Jan 2012 01:40:22 +0000 http://blog.httpwatch.com/2007/11/20/error_internet_invalid_url-httpwatch/#comment-64870 dear Eric Yan I have the same problem with you,I don't have a clue to solve this problem.Do you have any suggestions.I really appreciate it. Please forgive me for my poor english dear Eric Yan
I have the same problem with you,I don’t have a clue to solve this problem.Do you have any suggestions.I really appreciate it. Please forgive me for my poor english

]]> http://blog.httpwatch.com/2007/11/20/error_internet_invalid_url-httpwatch/comment-page-1/#comment-14186 Eric Yan Mon, 11 Jan 2010 07:42:17 +0000 http://blog.httpwatch.com/2007/11/20/error_internet_invalid_url-httpwatch/#comment-14186 I have the same library as esnouf. The first time i load the page,the http://:/ takes about 30 seconds,which it's serious impact the performance. I have the same library as esnouf.
The first time i load the page,the http://:/ takes about 30 seconds,which it’s serious impact the performance.

]]> http://blog.httpwatch.com/2007/11/20/error_internet_invalid_url-httpwatch/comment-page-1/#comment-7342 esnouf Sat, 13 Jun 2009 06:02:52 +0000 http://blog.httpwatch.com/2007/11/20/error_internet_invalid_url-httpwatch/#comment-7342 You have the same behavior using another library, named DOJO. If in HTTPwatch you see that such GET takes 0 seconds that is fine. If it takes more (I have seen 6 seconds) then it has a serious impact on the application performance. You should then replace the code and use a good URL to speedup the process. You can either change that on the application itself, or if you publish this application via a reverse proxy or a VPN/SSL, in the box itself if it has a "rewriting on the fly" technology. You have the same behavior using another library, named DOJO. If in HTTPwatch you see that such GET takes 0 seconds that is fine. If it takes more (I have seen 6 seconds) then it has a serious impact on the application performance. You should then replace the code and use a good URL to speedup the process. You can either change that on the application itself, or if you publish this application via a reverse proxy or a VPN/SSL, in the box itself if it has a “rewriting on the fly” technology.

]]> http://blog.httpwatch.com/2007/11/20/error_internet_invalid_url-httpwatch/comment-page-1/#comment-550 Detlev Beutner Wed, 25 Jun 2008 09:40:20 +0000 http://blog.httpwatch.com/2007/11/20/error_internet_invalid_url-httpwatch/#comment-550 At least on IE7 the replacement of "//:" by "about:blank" should do the trick (as far as I remember, on IE6 "about:blank" led to security warnings if called in an HTTP context). So - such JS lib providers maybe should change their implementation - the "about:blank" not only leads to no error message in httpWatch, but also generates to internal request at all, saving 1-3 millisecs. At least on IE7 the replacement of “//:” by “about:blank” should do the trick (as far as I remember, on IE6 “about:blank” led to security warnings if called in an HTTP context). So – such JS lib providers maybe should change their implementation – the “about:blank” not only leads to no error message in httpWatch, but also generates to internal request at all, saving 1-3 millisecs.

]]>