Debian Codegraph @

httpasyncclient-cache/src/test/java/org/apache/http/impl/client/cache/TestAsyncProtocolDeviations.java

raw
1 /*
2 * ====================================================================
3 * Licensed to the Apache Software Foundation (ASF) under one
4 * or more contributor license agreements. See the NOTICE file
5 * distributed with this work for additional information
6 * regarding copyright ownership. The ASF licenses this file
7 * to you under the Apache License, Version 2.0 (the
8 * "License"); you may not use this file except in compliance
9 * with the License. You may obtain a copy of the License at
10 *
11 * http://www.apache.org/licenses/LICENSE-2.0
12 *
13 * Unless required by applicable law or agreed to in writing,
14 * software distributed under the License is distributed on an
15 * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
16 * KIND, either express or implied. See the License for the
17 * specific language governing permissions and limitations
18 * under the License.
19 * ====================================================================
20 *
21 * This software consists of voluntary contributions made by many
22 * individuals on behalf of the Apache Software Foundation. For more
23 * information on the Apache Software Foundation, please see
24 * <http://www.apache.org/>.
25 *
26 */
27 package org.apache.http.impl.client.cache;
28
29 import org.apache.http.impl.execchain.ClientExecChain;
30
31 /**
32 * We are a conditionally-compliant HTTP/1.1 client with a cache. However, a lot of the rules for
33 * proxies apply to us, as far as proper operation of the requests that pass through us. Generally
34 * speaking, we want to make sure that any response returned from our HttpClient.execute() methods
35 * is conditionally compliant with the rules for an HTTP/1.1 server, and that any requests we pass
36 * downstream to the backend HttpClient are are conditionally compliant with the rules for an
37 * HTTP/1.1 client.
38 * <p>
39 * There are some cases where strictly behaving as a compliant caching proxy would result in strange
40 * behavior, since we're attached as part of a client and are expected to be a drop-in replacement.
41 * The test cases captured here document the places where we differ from the HTTP RFC.
42 */
43 public class TestAsyncProtocolDeviations extends TestProtocolDeviations {
44
45 @Override
46 protected ClientExecChain createCachingExecChain(
47 final ClientExecChain backend,
48 final HttpCache cache,
49 final CacheConfig config) {
50 return new CachingHttpAsyncClientExecChain(backend, cache, config);
51 }
52 }