Next: About this document ...
Up: Design for a Web
Previous: Summary
Following are the evalutation of the Web Proxy for various test cases.
- Transparency
- was checked with the following scenarios:
- GET request (http://www.cs.brandeis.edu/) works as
expected, correctly displaying the page.
- POST request works.
- HEAD request is handled as a GET request and passed
correctly through the proxy.
- Error 404 is correctly forwarded to the client.
- Reloading many times before web proxy response finishes
does not generate an error in the proxy.
- The Web proxy could handle early termination (by
pressing Stop in mid-download)
- The Web proxy correctly displays images/binary files.
- If-Modified-Since headers are passed transparently.
- Web caching
- was checked with the following:
- Web pages are cached on disk and the cache mapping is
written periodically to disk.
- For a cache hit, the page is sent directly to the
browser from the cache without connection to the remote server.
- There are no limits on cache size, which means that the
cache could fill the disk.
- The pages stored in cache are identical to those
received from the server.
- The proxy correctly obeys the Expires header.
- The proxy does not returned cached pages when given
Pragma:no-cache, which is correct.
- Non-blocking
- was also checked:
- The web proxy allows many simultaneous requests, since
it uses non-blocking system calls.
- Hanging server does not cause web proxy to hang.
- Hanging client does not cause web proxy to hang.
- Non-responding server does not hang the web proxy.
Next: About this document ...
Up: Design for a Web
Previous: Summary
Magnus Bjornsson
1998-05-08