: Network Disk Download
About the bookEdited by Gourlay, the HTTP authoritative guide explains in detail how HTTP can be used to develop web-based applications, how the core Internet Protocol interacts with architecture building blocks, how to properly implement Internet clients and servers, and so on. The central content of the HTTP authoritative guide is HTTP, which is essentially an understanding of how the Web works and how it can be applied to web programming and management, mainly covering the way HTTP works, its motivations, performance and goals, and related technical issues. The HTTP authoritative guide is for anyone who wants to learn about HTTP and the underlying structure of the web. Edit recommended Edit http (Hypertext Transfer Protocol, Hypertext Transfer Protocol) is the protocol used by web clients to interact with the server documents and information, and is behind every successful web transaction. As we all know, every day we visit the company's internal network, search out-of-print books, research statistics, the core of the browser used is HTTP. But the application of HTTP is far more than just browsing Web content. Because HTTP is both simple and pervasive, many other Web applications have chosen it, especially with the use of soap and XML-RPC.
Explains the HTTP protocol in detail, including how it works, and how it can be used to develop web-based applications. But this book does not only introduce HTTP, but also explores all the other core Internet technologies that HTTP works on. Although HTTP is the center of the book, the Essence of the book is to understand how the Web works and how to apply it to web programming and management, mainly covering the way HTTP works, the motivations, the performance and the goals, and some related technical issues.
This book is the HTTP protocol and related web technology works, the main content includes:
HTTP method, header, and status code
Ways to optimize proxies and caches
Strategies for designing web bots and crawlers
Cookies, authentication, and secure HTTP
Internationalization and content negotiation
Redirection and load Balancing strategies
For web development to be efficient, all web programmers, administrators, and application developers should be familiar with HTTP. Many books only describe how the Web is used, and this book provides an in-depth explanation of how the Web works.[1] Preface Edit Hypertext Transfer Protocol (hypertext Transfer Protocol,http) is the protocol scheme used to communicate on the World Wide Web. HTTP has many applications, but the most notable is the duplex communication between the Web browser and the Web server. HTTP is initially a simple protocol, so you might think there's not much to say about this protocol. But now you have a two-pound book in Your hand. If you're surprised at how we're going to write a 650-page book about HTTP, you can go to the table of contents. This book is not just a reference manual for the HTTP header; It is a veritable web-structured bible. In this book, we try to sort out some of the interrelated and often misunderstood rules in HTTP, and write a series of chapters based on various topics that describe the features of HTTP. Throughout the book, we have explained in detail the http "Why", not just how it is done. And, to save you time searching for references, we also introduce important non-HTTP technologies that are essential to the proper functioning of many HTTP applications. In an easy-to-use appendix, you can find the alphabetical first reference (these headers form the basis for the most common HTTP text). We hope this conceptual design will help readers to use HTTP. This book is written for anyone who wants to understand HTTP and the underlying structure of the web. Software and hardware engineers can also use this book as a well-organized reference for HTTP and related Web technologies. System architects and network administrators can use this book to better understand how to design, implement, and manage complex network architectures. Performance engineers and analysts can benefit from the relevant chapters of cache and performance optimization. Marketing and consulting experts can better understand the future of web technology through an introduction to concepts. This book explains some common misconceptions, recommends "various use tips", provides handy reference materials, and makes a very readable introduction to the tedious and confusing standard specifications. In this book, we describe in detail the technologies that are necessary and interrelated for the web to work properly. This book is a lot of work written by people who are passionate about Internet technology. I hope to be of some help to you. Running an instance: Joe's Hardware store many chapters of this book involve an imaginary online hardware and home furnishing store example that describes some of the technical concepts through the store called Joe Hardware. We have built a real web site for this store so that we can test some of the examples in the book. As long as the book is still on sale, we will always maintain this web site.[1] Author Profile Editor David Gourley is Endeca's chief technology officer (chief technology Officer), responsible for ENDECA product research and development. The Internet and Internal network information access solutions developed by Endeca provide some new ways for enterprise-level data navigation and research. Before Endeca to work, David was a member of the Inktomi Foundation Engineering group, where he helped develop the Inktomi Internet search database, the main developer of the Inktomi Web cache product. David received a bachelor's degree in computer science from the University of California, Berkeley, and several patents on web technology. Brian Totty recently served as vice president of research and Development at Inktomi (a company he founded in 1996), where he was responsible for Web caching, streaming and Internet search technology research and development. He was a scientist at Silicon Graphics, where he designed and optimized software for high-performance networks and supercomputer systems. Before that, he was an engineer at Apple's senior technology group. Brian received a PhD in computer science from the University of Illinois at Urbana-champaign and a bachelor's degree in computer science and electronic Engineering from MIT, where he received the Organick Award for computer system Research. He also developed and lectured on several award-winning Internet technology courses for the University of California extension system. Marjorie Sayer is responsible for writing software for Web caching in the Inktomi company. After obtaining a master's and a PhD in mathematics at UC Berkeley, he has been working on the reform of the mathematics curriculum. Since 1990, he has been working on energy resource management, parallel system software, telephone and web writing. Sailu Reddy is currently responsible for the development of embedded performance-enhanced HTTP proxies in Inktomi. Sailu has been engaged in the development of complex software systems for more than 12 years, and has been working on Web architecture since 1995. He is Netscape's first Web server, Web Proxy product, and core engineer for later generations of products. He has technical experience in HTTP applications, data compression technology, database engine, and cooperative management. Sailu a master's degree in Information Systems at Arizona University and holds a number of patents on web technology. Anshu Aggarwal is the engineering director of Inktomi Corporation. He led the Inktomi Company's protocol processing engineering group for Web cache products, and has been involved in Inktomi's web design work since 1997. Anshu a master's and PhD in computer Science from the University of Colorado at BoulderIn the research of distributed multi-processor memory consistency technology. He also holds a master's and bachelor's degree in electrical engineering. Anshu has authored several technical papers and has two patents.[2]Book Catalog Edit Catalog
The foundation of the first part of Http:web
1th. HTTP Overview 3
1.1 http--Multimedia Messenger of the Internet 4
1.2 Web client and server 4
1.3 Resources 5
1.3.1 Media type 6
1.3.2 URI 7
1.3.3 URL 7
1.3.4 URN 8
1.4 Transactions 9
1.4.1 Method 9
1.4.2 Status Code 10
1.4.3 can contain multiple objects in a Web page 10
1.5 Messages 11
1.6 Connection 13
1.6.1 TCP/IP 13
1.6.2 connection, IP address and port number 14
1.6.3 using Telnet instance 16
1.7 Protocol version 18
1.8 Structure components of the Web 19
1.8.1 Agent 19
1.8.2 Cache 20
1.8.3 Gateway 20
1.8.4 Tunnel 21
1.8.5 Agent 21
1.9 Concluding remarks of the starting part 22
1.10 More Information 22
1.10.1 HTTP Protocol Information 22
1.10.2 Historical Perspective 23
1.10.3 Other World Wide Web information 23
2nd Chapter URL and Resources 25
2.1 Browse Internet Resources 26
Syntax for 2.2 URLs 28
2.2.1 Scenario-what protocol to use 29
2.2.2 Host and Port 30
2.2.3 User name and password 30
2.2.4 Path 31
2.2.5 parameter 31
2.2.6 Query string 32
2.2.7 Fragment 33
2.3 URL Shortcut 34
2.3.1 Relative URL 34
2.3.2 Automatic Extension URL 37
2.4 Various vexing characters 38
2.4.1 URL Character Set 38
2.4.2 Encoding Mechanism 38
2.4.3 Character limit 39
2.4.4 Another point of note 40
2.5 scenario of the World 40
2.6 Future Prospects 42
2.7 More information 44
3rd. HTTP Message 45
3.1 Message Stream 46
3.1.1 Messages to source-side server 46
3.1.2 Message flows downstream 47
3.2 Components of the message 47
Syntax for 3.2.1 Messages 48
3.2.2 Start line 50
3.2.3 First Part 53
3.2.4 the body part of the entity 55
3.2.5 version 0.9 of message 55
3.3 Method 56
3.3.1 Security Method 56
3.3.2 GET 56
3.3.3 HEAD 57
3.3.4 PUT 57
3.3.5 POST 58
3.3.6 TRACE 58
3.3.7 OPTIONS 60
3.3.8 DELETE 60
3.3.9 extension Method 61
3.4 Status Code 62
3.4.1 100 ~ 199--Informational Status Code 62
3.4.2 200 ~ 299--Success Status Code 63
3.4.3 300 ~ 399--REDIRECT Status Code 64
3.4.4 400 ~ 499--Client Error Status code 68
3.4.5 500 ~ 599--Server Error Status Code 69
3.5 First Part 70
3.5.1 Universal Header 71
3.5.2 Request Header 72
3.5.3 Response Header 74
3.5.4 Entity Header 75
3.6 More Information 77
Chapter 4th Connection Management 79
4.1 TCP Connection 80
4.1.1 Reliable data pipeline for TCP 80
4.1.2 TCP streams are fragmented and routed by IP packets 81
4.1.3 Keeping the TCP connection running correctly 82
4.1.4 Programming with TCP sockets 84
4.2 Considerations for TCP Performance 85
4.2.1 Latency for HTTP Transactions 86
4.2.2 Performance Focus Area 87
4.2.3 Handshake time delay for TCP connections 87
4.2.4 Delay Confirmation 88
4.2.5 TCP Slow start 89
4.2.6 Nagle algorithm and Tcp_nodelay 89
4.2.7 time_wait Cumulative and Port depletion 90
4.3 Processing of HTTP connections 91
4.3.1 often misunderstood connection header 91
4.3.2 Serial transaction processing time delay 92
4.4 Parallel Connections 94
4.4.1 Parallel connection may increase page load speed by 94
4.4.2 parallel connections are not necessarily faster 95
4.4.3 Parallel connections may make people "feel" a bit faster 95
4.5 Persistent Connection 96
4.5.1 Persistent and parallel connections 96
4.5.2 http/1.0+ keep-alive Connection 97
4.5.3 keep-alive Operation 98
4.5.4 keep-alive Option 98
4.5.5 restrictions and rules for keep-alive connections 99
4.5.6 keep-alive and Dummy Agent 100
4.5.7 inserting Proxy-connection 102
4.5.8 http/1.1 Persistent Connection 104
4.5.9 restrictions and rules for persistent connections 104
4.6 Plumbing Connection 105
4.7 Closing the mystery of the connection 106
4.7.1 "any" disconnect 106
4.7.2 Content-length and truncated operation 107
4.7.3 connection Close tolerance, retry, and Idempotent 107
4.7.4 Normal shutdown Connection 108
4.8 More Information 110
4.8.1 HTTP Connection 110
4.8.2 HTTP Performance Issues 110
4.8.3 TCP/IP 111
Part Two HTTP structure
Chapter 5th WEB Server 115
5.1 Web servers in various shapes and sizes 116
5.1.1 implementation of the WEB server 116
5.1.2 Universal Software Web server 117
5.1.3 Web Server Devices 117
5.1.4 Embedded Web server 118
5.2 The smallest Perl Web server 118
5.3 What the actual Web server will do 120
5.4 First Step--Accept Client Connection 121
5.4.1 Handling New Connections 121
5.4.2 Client host name recognition 122
5.4.3 determining client users by Ident 122
5.5 Second Step-Receive request message 123
Internal representation of 5.5.1 messages 124
5.5.2 connected input/output processing structure 125
5.6 Step three-handling requests 126
5.7 Fourth Step-mapping and access to resources 126
5.7.1 Docroot 127
5.7.2 Directory listing 129
5.7.3 mapping of dynamic content resources 130
5.7.4 server-side contains items 131
5.7.5 Access Control 131
5.8 Fifth Step-build response 131
5.8.1 Response Entity 131
5.8.2 MIME Type 132
5.8.3 REDIRECT 133
5.9 Sixth Step-send response 134
5.10 Seventh Step--Logging 134
5.11 More Information 134
6th Chapter Agent 135
6.1 Intermediate entities of the WEB 136
6.1.1 Private and shared proxies 136
6.1.2 Proxy vs. Gateway 137
6.2 Why use a proxy 138
6.3 Where will the agent go 143
6.3.1 deployment of proxy servers 144
6.3.2 Hierarchy of Agents 144
How the 6.3.3 agent gets 147 of the traffic
6.4 Proxy settings for clients 148
Agent configuration for 6.4.1 clients: manual configuration 149
6.4.2 Client Agent configuration: PAC file 149
6.4.3 Client Agent configuration: WPAD 150
6.5 Some tricky questions about proxy requests 151
6.5.1 proxy URI differs from server URI 151
6.5.2 the same problem as a virtual host 152
6.5.3 Intercept Agent will receive a partial URI 153
The 6.5.4 agent can handle either proxy requests or server requests 154
6.5.5 modification of URIs during forwarding 154
6.5.6 URI Client Auto-scaling and hostname resolution 155
6.5.7 parsing of URIs when there is no proxy 155
6.5.8 parsing of URIs with explicit proxy 156
6.5.9 URI parsing when interception agent is available 157
6.6 Tracking Messages 158
6.6.1 Via Header 158
6.6.2 TRACE Method 162
6.7 Agent Certification 164
6 | Directory
6.8 Interoperability of proxies 165
6.8.1 processing agent not supported headers and methods 166
6.8.2 Options: Discover support for optional features 166
6.8.3 Allow header 167
6.9 More Information 167
7th Chapter Cache 169
7.1 Redundant data transfer 170
7.2 Bandwidth Bottleneck 170
7.3 Momentary Congestion 171
7.4 Distance delay 172
7.5 Hits and misses of 173
7.5.1 Re-authentication 173
7.5.2 hit Ratio 175
7.5.3-byte hit ratio 176
7.5.4 distinguishing between hit and miss scenarios 176
7.6 Topology of the cache 177
7.6.1 Private Cache 177
7.6.2 Public Proxy Cache 177
7.6.3 hierarchy of proxy caches 179
7.6.4 mesh cache, content routing, and peer caching 180
7.7 Processing steps for caching 181
7.7.1 first Step--Receive 181
7.7.2 Second Step--analysis 182
7.7.3 Step Three--Find 182
7.7.4 Fourth Step-freshness detection 182
7.7.5 Fifth Step--Create response 182
7.7.6 The sixth step--Send 183
7.7.7 Seventh Step--Log 183
7.7.8 Cache processing Flowchart 183
7.8 Keeping a copy fresh 183
7.8.1 Document expires 184
7.8.2 expiration date and usage period 185
7.8.3 Server re-authentication 185
7.8.4 using conditional method to re-verify 186
7.8.5 If-modified-since:date re-verification 187
7.8.6 If-none-match: Entity label re-authentication 189
7.8.7 Strength Authenticator 190
7.8.8 when should I use Entity tags and last modified date 190
7.9 ability to control caching 191
7.9.1 No-store and No-cache response header 191
7.9.2 Max-age Response Header 192
7.9.3 Expires Response Header 192
7.9.4 Must-revalidate Response Header 192
7.9.5 Tentative Expiration 193
7.9.6 client's freshness limit 194
7.9.7 Precautions 194
7.10 Setting the cache control 195
7.10.1 control Apache HTTP Header 195
7.10.2 controlling HTML cache by HTTP-EQUIV 196
7.11 Detailed algorithm 197
7.11.1 period and freshness Lifetime 198
Calculation of 7.11.2 usage period 198
7.11.3 full use-time Calculation algorithm 201
7.11.4 Fresh Lifetime Calculation 202
7.11.5 Full server-freshness algorithm 202
7.12 Caching and Advertising 204
7.12.1 the dilemma of publishing advertisers 204
7.12.2 the publisher's response 204
7.12.3 Log Migration 205
7.12.4 hit count and usage limit 205
7.13 More Information 205
8th Integration Point: gateways, tunnels, and relays 207
8.1 Gateway 208
8.2 Protocol Gateway 210
8.2.1 http/*: Server-side web Gateway 211
8.2.2 Http/https: Server-side Security Gateway 212
8.2.3 Https/http Client Security Accelerator Gateway 212
8.3 Resource Gateway 213
8.3.1 CGI 215
8.3.2 Server Extensions API 215
8.4 Application interfaces and Web services 216
8.5 Tunnel 217
8.5.1 using connect to create an HTTP tunnel 217
8.5.2 data tunneling, timing and connection management 219
8.5.3 SSL Tunnel 219
8.5.4 SSL Tunnel vs. Http/https Gateway 220
8.5.5 Tunnel Certification 221
Safety Considerations for 8.5.6 Tunnels 221
8.6 Trunks 222
8.7 More Information 224
9th Web Robot 225
9.1 Crawler and crawling mode 226
Where to start 9.1.1: the root set 226
Extraction of 9.1.2 links and standardization of relative links 227
9.1.3 avoid the advent of loops 228
9.1.4 Cycle and Replication 228
9.1.5 traces left by the bread crumbs 229
9.1.6 aliases and Robot loops 230
9.1.7 Normalization URL 230
9.1.8 File system Connection Loop 231
9.1.9 Dynamic Virtual Web space 232
9.1.10 avoiding loops and repetitions 233
9.2 The HTTP 236 of the robot
9.2.1 Recognition Request Header 236
9.2.2 Virtual Host 236
9.2.3 Condition Request 237
9.2.4 Handling of responses 238
9.2.5 user-agent Guide 239
9.3 Improper behavior of the robot 239
9.4 Deny bot access 240
9.4.1 deny Android Access standard 241
9.4.2 Web Site and robots.txt file 242
9.4.3 format of robots.txt file 243
9.4.4 other knowledge about robots.txt 246
Expiration of 9.4.5 cache and robots.txt 246
9.4.6 perl code to deny bot access 246
9.4.7 HTML Robot-control META tags 249
9.5 Specification for Robots 251
9.6 Search engine 254
9.6.1 Large Pattern 255
9.6.2 Modern search engine structure 255
9.6.3 Full-Text index 255
9.6.4 Publishing a query request 257
9.6.5 sorting results and providing query results 258
9.6.6 Fraud 258
9.7 More Information 258
10th Chapter Http-ng 261
10.1 Problems in the development of HTTP 262
Activities of 10.2 http-ng 263
10.3 modularity and Function enhancement 263
10.4 Distributed Objects 264
10.5 First Layer--message transfer 264
10.6 Second Layer-Remote call 265
10.7 Third tier--web application 265
10.8 Webmux 265
10.9 Binary Connection Protocol 266
10.10 Current Status 267
10.11 More Information 267
Part III identification, authentication and security
11th. Client identification and cookie mechanism 271
11.1 Sexual contacts 272
11.2 HTTP Header 273
11.3 Client IP Address 274
11.4 User Login 275
11.5 Fat URL 277
11.6 Cookie 278
11.6.1 Types of Cookies 278
How the 11.6.2 cookie works 279
11.6.3 cookie jar: Status of the client 280
11.6.4 different sites using different cookies 282
11.6.5 Cookie Ingredient 283
11.6.6 Cookies version 0 (Netscape) 284
11.6.7 Cookies version 1 (RFC 2965) 285
11.6.8 cookie Session Tracking 288
11.6.9 Cookies and caches 290
11.6.10 cookies, security and privacy 291
11.7 More Information 292
The 12th Chapter Basic authentication mechanism 293
12.1 Certification 294
12.1.1 HTTP Challenge/Response Authentication Framework 294
12.1.2 Certification Agreement and header 295
12.1.3 Security Domain 296
12.2 Basic Certifications 297
12.2.1 Basic Authentication Example 298
12.2.2 Base-64 username/password Code 298
12.2.3 Agent Certification 299
12.3 Basic certifications for security defects 300
12.4 More Information 301
13th Chapter Summary Certification 303
13.1 Summary Certification Improvements 304
13.1.1 protect password with digest 304
13.1.2 One-way Summary 306
13.1.3 using random numbers to prevent replay attacks 307
13.1.4 Digest-certified handshake mechanism 307
13.2 Calculation of the digest 308
13.2.1 Digest algorithm input data 308
13.2.2 algorithm H (d) and KD (s,d) 310
13.2.3 Security-related data (A1) 310
13.2.4 data related to messages (A2) 310
13.2.5 Summary Algorithm Overview 311
13.2.6 Digest Authentication Session 312
13.2.7 Pre-Authorization 312
13.2.8 selection of random numbers 315
13.2.9 Symmetry Certification 315
13.3 Enhanced protection Quality 316
13.3.1 Message Integrity Protection 316
13.3.2 Digest Certification Header 317
13.4 practical issues to be considered 317
13.4.1 Multi-Challenge 318
13.4.2 Error Handling 318
13.4.3 Protective Space 318
13.4.4 rewrite URI 319
13.4.5 Cache 319
13.5 Security Considerations 320
13.5.1 First Tamper 320
13.5.2 Replay Attack 320
13.5.3 Multi-authentication mechanism 320
13.5.4 Dictionary Attack 321
13.5.5 malicious agent attack and man-in-the-middle attack 321
13.5.6 Select plaintext Attack 321
13.5.7 Storage Password 322
13.6 More information 322
14th. Security HTTP 323
14.1 Security for HTTP protection 324
14.2 Digital Encryption 326
The mechanism and technique of 14.2.1 cryptography 326
14.2.2 Password 327
14.2.3 Password Machine 328
14.2.4 password used for key 328
14.2.5 Digital Password 328
14.3 symmetric key Encryption technology 330
14.3.1 key length and enumeration attack 330
14.3.2 establishing a shared key 332
14.4 Public key Encryption Technology 332
14.4.1 RSA 333
14.4.2 Hybrid encryption system and session key 334
14.5 Digital Signatures 334
14.6 Digital certificate 336
Main contents of the 14.6.1 certificate 336
14.6.2 V3 Certificate 337
14.6.3 authenticating the server with a certificate 338
14.7 https--Detail Introduction 339
14.7.1 HTTPS Overview 339
14.7.2 HTTPS Scenario 340
14.7.3 Establishing secure Transport 341
14.7.4 SSL Handshake 341
14.7.5 Server Certificate 343
14.7.6 the validity of the site certificate 344
14.7.7 Virtual Host and certificate 345
14.8 HTTPS Client Instance 345
14.8.1 OpenSSL 346
14.8.2 Simple HTTPS Client 347
14.8.3 performing OpenSSL client 350
14.9 transport of safe traffic via proxy in tunnel form 351
14.10 More Information 353
14.10.1 HTTP Security 353
14.10.2 SSL and TLS 353
14.10.3 Public Key Infrastructure 354
14.10.4 Digital Password 354
Part IV entity, coding and internationalization
Chapter 15th entities and codes 357
15.1 message is box, entity is cargo 359
15.2 content-length: Size of the entity 361
15.2.1 Detection Intercept 361
15.2.2 Error Content-length 362
15.2.3 content-length with persistent connection 362
15.2.4 Content Encoding 362
15.2.5 rules for determining the length of an entity body 362
15.3 Entity Summary 364
15.4 Media type and character set 364
15.4.1 character encoding for text 365
15.4.2 sub-media type 365
15.4. More than 3 sub-forms submitted 366
15.4.4 + Range Response 367
15.5 Content Encoding 368
15.5.1 content Encoding Process 368
15.5.2 content Encoding Type 369
15.5.3 accept-encoding Header 369
15.6 transmission encoding and chunked encoding 371
15.6.1 Reliable Transmission 371
15.6.2 transfer-encoding Header 372
15.6.3 chunked Encoding 373
15.6.4 combination of content encoding and transmission encoding 375
15.6.5 rules for transmission encoding 375
15.7 examples of time-varying 375
15.8 Verification code and freshness 376
15.8.1 Freshness 377
15.8.2 conditional request and Verification Code 378
15.9 Range Request 380
15.10 Difference Code 382
15.11 More information 385
Chapter 16th Internationalization 387
16.1 HTTP support for international content 388
16.2 Character set with HTTP 389
The 16.2.1 character set is an encoding that converts a character to a binary code 389
How 16.2.2 character set and encoding works 390
16.2.3 character set is wrong, character is not 391
16.2.4 normalized MIME CharSet value 391
16.2.5 Content-type Header and CharSet header and Meta Flag 393
16.2.6 Accept-charset Header 393
16.3 Getting started with multi-language character encoding 394
16.3.1 Character Set Terminology 394
The 16.3.2 character set is poorly named 395
16.3.3 characters 396
16.3.4, ligatures, and representations 396
16.3.5 encoded Character Set 397
16.3.6 character encoding scheme 399
16.4 Language tags with http 402
16.4.1 Content-language Header 402
16.4.2 Accept-language Header 403
16.4.3 Types of Language tags 404
16.4.4 Sub-tag 404
16.4.5 Case 405
16.4.6 IANA language Tag Registration 405
16.4.7 first child tag--namespaces 405
16.4.8 Second sub-tag--namespaces 406
16.4.9 remaining sub-tags--namespace 407
16.4.10 Configuration and language-related preferences 407
16.4.11 Language Tag Reference table 407
16.5 internationalization of the URI 408
16.5.1 global ability to compete with meaningful characters in copied 408
16.5.2 URI Character Set 408
16.5.3 escaping and Reversing righteousness 409
16.5.4 escaping internationalized characters 409
16.5.5 modal switchover in URI 410
16.6 Other places to consider 410
16.6.1 First and non-canonical data 410
16.6.2 Date 411
16.6.3 Domain 411
16.7 More Information 411
16.7.1 Appendix 411
16.7.2 internationalization of the Internet 411
16.7.3 International Standard 412
17th Chapter Content Negotiation and transcoding 413
17.1 Content Negotiation Technology 414
17.2 Client-driven negotiation 415
17.3 Server-Driven negotiation 415
17.3.1 content Negotiation Header set 416
17.3.2 quality value in content negotiation header 417
17.3.3 changes with other header sets 417
17.3.4 content negotiation in Apache 417
17.3.5 server-side extensions 418
17.4 Transparent Negotiation 419
17.4.1 Cache and Standby candidate 419
17.4.2 Vary Header 420
17.5 transcoding 422
17.5.1 Format Conversion 422
17.5.2 Information Synthesis 423
17.5.3 Content Injection 423
17.5.4 transcoding vs. static pre-generation 423
17.6 Next Plan 424
17.7 More information 424
Part V Content Publishing and distribution
18th. Web Hosting 429
18.1 colocation Services 430
18.2 Virtual Hosting 431
18.2.1 Virtual Server request lacks host information 432
18.2.2 trying to get virtual hosting to work properly 433
18.2.3 http/1.1 's host header 437
18.3 making your site more reliable 438
18.3.1 server clusters for mirroring 438
18.3.2 Content Distribution Network 440
18.3.3 reverse proxy cache in CDN 440
18.3.4 Proxy cache in CDN 440
18.4 Make website Faster 441
18.5 More Information 441
19th. Release system 443
19.1 FrontPage Server Extensions for publishing support 444
19.1.1 FrontPage Server Extensions 444
19.1.2 FrontPage Glossary 445
19.1.3 FrontPage RPC Protocol 445
19.1.4 FrontPage's security model 448
19.2 WebDAV and Collaborative writing 449
19.2.1 Methods of WebDAV 449
19.2.2 WebDAV with XML 450
19.2.3 WebDAV Header Episode 451
19.2.4 WebDAV Lock and prevent overwrite 452
19.2.5 LOCK Method 453
19.2.6 UNLOCK Method 456
19.2.7 properties and meta-data 456
19.2.8 PROPFIND Method 457
19.2.9 PROPPATCH Method 459
19.2.10 collection and Namespace management 460
19.2.11 Mkcol Method 460
19.2.12 DELETE Method 461
19.2.13 COPY and Move method 462
19.2.14 Enhanced http/1.1 Method 465
19.2.15 version Management in WebDAV 466
19.2.16 future development of WebDAV 466
19.3 More information 467
20th Redirect and load balancer 469
20.1 Why redirect 470
20.2 Redirect to where 471
20.3 Redirection Protocol Overview 471
20.4 Generic Redirection Method 474
20.4.1 HTTP Redirection 474
20.4.2 DNS Redirection 475
20.4.3 anycast Addressing 480
20.4.4 IP MAC Forwarding 481
20.4.5 IP Address Forwarding 482
20.4.6 Network Element Control Protocol 484
20.5 redirection methods for proxies 485
20.5.1 Explicit Browser Configuration 485
20.5.2 Proxy automatic Configuration 485
20.5.3 Web Proxy Autodiscover Protocol 487
20.6 Cache Redirection Method 492
20.7 Internet Cache Protocol 496
20.8 Cache Array Routing protocol 497
20.9 Hypertext Caching Protocol 500
20.9.1 HTCP Certification 502
20.9.2 Setting the cache policy 503
20.10 More Information 504
21st. Log record and Usage tracking 505
21.1 Record Content 506
21.2 Log Format 507
21.2.1 Common Log Formats 507
21.2.2 Combined Log Format 508
21.2.3 Netscape Extended Log format 509
21.2.4 Netscape Expansion 2nd log format 510
21.2.5 SQUID Agent Log Format 512
21.3 Hit rate measurement 515
21.3.1 Overview 515
21.3.2 Meter Header 516
21.4 Consideration of privacy 517
21.5 More Information 518
Part VI Appendix
Appendix A URI Scheme 521
Appendix B HTTP Status Code 529
Appendix C HTTP Header Reference 533
Appendix D MIME Type 557
Appendix E Base-64 Code 603
Appendix F Summary Certification 607
Appendix G Language Tags 615
Appendix H MIME Character Set Registry 641
: Network Disk Download
"HTTP authoritative guide" HD Chinese version pdf
