Figure 4-8: A generic error message created when an unrecognized file extension is
requested
Using the automated content discovery techniques already described, it is
possible to request a large number of common file extensions and quickly con-
firm whether any of the associated technologies are implemented on the
server.
The divergent behavior described arises because many web servers map
specific file extensions to particular server-side components. Each different
component may handle errors (including requests for nonexistent content) in
a different way. Figure 4-9 shows the various extensions that are mapped to
different handler DLLs in a default installation of IIS 5.0.
Do'stlaringiz bilan baham: