- Recent
- Popular
- Tags (0)
- Subscribers (3)
- HttpWatch is a Jolt Finalist!December 19 2008
-
We are pleased to announce that HttpWatch is a finalist in the Utilities category of the 19th Jolt Product Excellence Awards.The Jolt Product Excellence Awards are run by CMP Technology’s Dr. Dobb’s. For the past 18 years, the Jolt awards have been presented annually to showcase products that have “jolted” the industry with their significance and made the task of creating software faster, easier, and more efficient.
The final winner in each category will be announced March 11, 2009 at the SD West conference in Santa Clara, CA.
- Firefox 3.1 Beta 2December 10 2008
-
The latest update to HttpWatch supports the recently released Firefox 3.1 Beta 2. This beta provides some significant new features to Firefox including:- A new faster Javascript engine called TraceMonkey
- Web worker threads
- JavaScript query selectors
- Google Adds HTTPS Support to the Ajax Libraries APINovember 27 2008
-
Our blog post ‘Test Drive of the Google Hosted Ajax Libraries‘ looked at using Google’s CDN (Content Delivery Network) to serve up commonly used libraries such as jQuery and Prototype.
One significant advantage, that we found, was that downloading a library from a different hostname (i.e. ajax.googleapis.com) helps to avoid the HTTP connection limiting behavior that causes blocking in browsers:
There are other significant advantages to using Google hosted libraries:
- The libraries are hosted on Google’s high speed global network providing fast access from most locations world wide
- HTTP compression minimizes the size of the download
- Minimized versions of the each library are available to further reduce download size
- The library that your site uses may already be in the user’s browser cache if the user has
- IE will be more secure when Sun fix Java bug 6545701November 12 2008
-
One of the most common security vulnerabilities in Windows software is the buffer overrun exploit. It works by feeding a well crafted data stream into a program that uses a stack based buffer without correctly checking the length of the data stream. By writing past the end of the buffer the overwrite can:
- Store malicious assembler instructions in the stack’s memory pages
- Change the current function’s return address on the stack so that the malicious instructions are executed instead of the original calling code hwne the function returns.
This technique for injecting code can be used to take control of the current process and possibly the whole PC if the program is running as a user with admin rights.
The problem originates from the fact that Intel’s early x86 processors would enforce the READ and WRITE flags on memory pages; but not the EXECUTE flag that is used for executable code pages. The memory pages used by a program’s stack never have the EXECUTE flag and step 2) above should fail because an attempt is being made to execute READ/WRITE data.
By the time Intel added the NX flag to enforce execution protection, many carelessly written programs relied on being able to execute code in a non-EXECUTE page. So when Microsoft added
- Using HttpWatch with WatiNOctober 30 2008
-
WatiN (pronounced as What-in) is a browser automation library for .NET that was inspired by the Ruby based Watir and FireWatir frameworks. It allows C# and VB.Net applications to programatically interact with a browser to perform tasks such as going to a web page, filling out fields and clicking on buttons. The current version only works with IE, but version 2.0 will include support for Firefox.
We have previously discussed the use of Ruby, Watir and HttpWatch and version 6.0 now contains Watir sample code that works with both IE and Firefox. HttpWatch can also be used alongside WatiN to record HTTP traffic and performance statistics while running an automated script. We adapted the Getting Started WatiN sample to use HttpWatch to record the Google results page. The modified code is shown below:
using System; using WatiN.Core; namespace
