Abstract
Until now, you’ve seen Apache more or less as an arbitrator between a client and a collection of files in a directory structure on the server. The client simply requests resources by listing their location in the directory hierarchy. However, HTTP can be much more subtle than this, and so can Apache.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
Rights and permissions
Copyright information
© 2004 Peter Wainwright
About this chapter
Cite this chapter
Wainwright, P. (2004). Deciding What the Client Needs. In: Pro Apache. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4302-0658-3_5
Download citation
DOI: https://doi.org/10.1007/978-1-4302-0658-3_5
Publisher Name: Apress, Berkeley, CA
Print ISBN: 978-1-59059-300-4
Online ISBN: 978-1-4302-0658-3
eBook Packages: Springer Book Archive