2 File: CustomHTTPProtocol.h
3 Abstract: An NSURLProtocol subclass that overrides the built-in HTTP/HTTPS protocol.
6 Disclaimer: IMPORTANT: This Apple software is supplied to you by Apple
7 Inc. ("Apple") in consideration of your agreement to the following
8 terms, and your use, installation, modification or redistribution of
9 this Apple software constitutes acceptance of these terms. If you do
10 not agree with these terms, please do not use, install, modify or
11 redistribute this Apple software.
13 In consideration of your agreement to abide by the following terms, and
14 subject to these terms, Apple grants you a personal, non-exclusive
15 license, under Apple's copyrights in this original Apple software (the
16 "Apple Software"), to use, reproduce, modify and redistribute the Apple
17 Software, with or without modifications, in source and/or binary forms;
18 provided that if you redistribute the Apple Software in its entirety and
19 without modifications, you must retain this notice and the following
20 text and disclaimers in all such redistributions of the Apple Software.
21 Neither the name, trademarks, service marks or logos of Apple Inc. may
22 be used to endorse or promote products derived from the Apple Software
23 without specific prior written permission from Apple. Except as
24 expressly stated in this notice, no other rights or licenses, express or
25 implied, are granted by Apple herein, including but not limited to any
26 patent rights that may be infringed by your derivative works or by other
27 works in which the Apple Software may be incorporated.
29 The Apple Software is provided by Apple on an "AS IS" basis. APPLE
30 MAKES NO WARRANTIES, EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION
31 THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY AND FITNESS
32 FOR A PARTICULAR PURPOSE, REGARDING THE APPLE SOFTWARE OR ITS USE AND
33 OPERATION ALONE OR IN COMBINATION WITH YOUR PRODUCTS.
35 IN NO EVENT SHALL APPLE BE LIABLE FOR ANY SPECIAL, INDIRECT, INCIDENTAL
36 OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
37 SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
38 INTERRUPTION) ARISING IN ANY WAY OUT OF THE USE, REPRODUCTION,
39 MODIFICATION AND/OR DISTRIBUTION OF THE APPLE SOFTWARE, HOWEVER CAUSED
40 AND WHETHER UNDER THEORY OF CONTRACT, TORT (INCLUDING NEGLIGENCE),
41 STRICT LIABILITY OR OTHERWISE, EVEN IF APPLE HAS BEEN ADVISED OF THE
42 POSSIBILITY OF SUCH DAMAGE.
44 Copyright (C) 2013 Apple Inc. All Rights Reserved.
48 #import <Foundation/Foundation.h>
50 @protocol CustomHTTPProtocolDelegate;
52 @interface CustomHTTPProtocol : NSURLProtocol
54 // Subclass specific additions
57 // Call this to start the module. Prior to this the module is just dormant, and
58 // all HTTP requests proceed as normal. After this all HTTP and HTTPS requests
59 // go through this module.
61 // The delegate is not retained in general, but is retained for the duration of any given
62 // call. Once you set the delegate to nil you can be assured that it won't be called
63 // unretained (that is, by the time that -setDelegate: returns, we've already done
64 // all possible retains on the delegate).
66 + (id<CustomHTTPProtocolDelegate>)delegate;
67 + (void)setDelegate:(id<CustomHTTPProtocolDelegate>)newValue;
76 The delegate handles two different types of callbacks:
78 o authentication challenges
81 The latter is very simple. The former is quite tricky. The basic idea is that each CustomHTTPProtocol
82 sends the delegate a serialised stream of authentication challenges, each of which it is expected to
83 resolve. The sequence is as follows:
85 1. It calls -customHTTPProtocol:canAuthenticateAgainstProtectionSpace: to determine if your delegate
86 can handle the challenge. This can be call on an arbitrary background thread.
88 2. If the delegate returns YES, it calls -customHTTPProtocol:didReceiveAuthenticationChallenge: to
89 actually process the challenge. This is always called on the main thread. The delegate can resolve
90 the challenge synchronously (that is, before returning from the call) or it can return from the call
91 and then, later on, resolve the challenge. Resolving the challenge involves calling
92 -[CustomHTTPProtocol resolveAuthenticationChallenge:withCredential:], which also must be called
93 on the main thread. Between the calls to -customHTTPProtocol:didReceiveAuthenticationChallenge:
94 and -[CustomHTTPProtocol resolveAuthenticationChallenge:withCredential:], the protocol's
95 pendingChallenge property will contain the challenge.
97 3. While there is a pending challenge, the protocol may call -customHTTPProtocol:didCancelAuthenticationChallenge:
98 to cancel the challenge. This is always called on the main thread.
101 @protocol CustomHTTPProtocolDelegate <NSObject>
106 - (void)customHTTPProtocol:(CustomHTTPProtocol *)protocol didRecieveResponse:(NSURLResponse *)response;
107 - (void)customHTTPProtocol:(CustomHTTPProtocol *)protocol didRecieveData:(NSData *)data;
108 - (void)customHTTPProtocolDidFinishLoading:(CustomHTTPProtocol *)protocol;
109 - (void)customHTTPProtocol:(CustomHTTPProtocol *)protocol didFailWithError:(NSError *)error;
112 - (void)customHTTPProtocol:(CustomHTTPProtocol *)protocol logWithFormat:(NSString *)format arguments:(va_list)argList;
113 // called on an arbitrary thread
114 // protocol may be nil, implying a log message from the class itself
115 // format will not be nil