appium-webdriveragent 16.6.0 → 16.7.0

package/WebDriverAgentLib/Vendor/CocoaHTTPServer/HTTPLogging.h

@@ -1,122 +0,0 @@
-/**
- * In order to provide fast and flexible logging, this project uses Cocoa Lumberjack.
- * 
- * The Google Code page has a wealth of documentation if you have any questions.
- * https://github.com/robbiehanson/CocoaLumberjack
- * 
- * Here's what you need to know concerning how logging is setup for CocoaHTTPServer:
- * 
- * There are 4 log levels:
- * - Error
- * - Warning
- * - Info
- * - Verbose
- * 
- * In addition to this, there is a Trace flag that can be enabled.
- * When tracing is enabled, it spits out the methods that are being called.
- * 
- * Please note that tracing is separate from the log levels.
- * For example, one could set the log level to warning, and enable tracing.
- * 
- * All logging is asynchronous, except errors.
- * To use logging within your own custom files, follow the steps below.
- * 
- * Step 1:
- * Import this header in your implementation file:
- * 
- * #import "HTTPLogging.h"
- * 
- * Step 2:
- * Define your logging level in your implementation file:
- * 
- * // Log levels: off, error, warn, info, verbose
- * static const int httpLogLevel = HTTP_LOG_LEVEL_VERBOSE;
- * 
- * If you wish to enable tracing, you could do something like this:
- * 
- * // Debug levels: off, error, warn, info, verbose
- * static const int httpLogLevel = HTTP_LOG_LEVEL_INFO | HTTP_LOG_FLAG_TRACE;
- * 
- * Step 3:
- * Replace your NSLog statements with HTTPLog statements according to the severity of the message.
- * 
- * NSLog(@"Fatal error, no dohickey found!"); -> HTTPLogError(@"Fatal error, no dohickey found!");
- * 
- * HTTPLog works exactly the same as NSLog.
- * This means you can pass it multiple variables just like NSLog.
- **/
-
-// Define logging context for every log message coming from the HTTP server.
-// The logging context can be extracted from the DDLogMessage from within the logging framework,
-// which gives loggers, formatters, and filters the ability to optionally process them differently.
-
-#define HTTP_LOG_CONTEXT 80
-
-// Configure log levels.
-
-#define HTTP_LOG_FLAG_ERROR   (1 << 0) // 0...00001
-#define HTTP_LOG_FLAG_WARN    (1 << 1) // 0...00010
-#define HTTP_LOG_FLAG_INFO    (1 << 2) // 0...00100
-#define HTTP_LOG_FLAG_VERBOSE (1 << 3) // 0...01000
-
-#define HTTP_LOG_LEVEL_OFF     0                                              // 0...00000
-#define HTTP_LOG_LEVEL_ERROR   (HTTP_LOG_LEVEL_OFF   | HTTP_LOG_FLAG_ERROR)   // 0...00001
-#define HTTP_LOG_LEVEL_WARN    (HTTP_LOG_LEVEL_ERROR | HTTP_LOG_FLAG_WARN)    // 0...00011
-#define HTTP_LOG_LEVEL_INFO    (HTTP_LOG_LEVEL_WARN  | HTTP_LOG_FLAG_INFO)    // 0...00111
-#define HTTP_LOG_LEVEL_VERBOSE (HTTP_LOG_LEVEL_INFO  | HTTP_LOG_FLAG_VERBOSE) // 0...01111
-
-// Setup fine grained logging.
-// The first 4 bits are being used by the standard log levels (0 - 3)
-// 
-// We're going to add tracing, but NOT as a log level.
-// Tracing can be turned on and off independently of log level.
-
-#define HTTP_LOG_FLAG_TRACE   (1 << 4) // 0...10000
-
-// Setup the usual boolean macros.
-
-#define HTTP_LOG_ERROR   (httpLogLevel & HTTP_LOG_FLAG_ERROR)
-#define HTTP_LOG_WARN    (httpLogLevel & HTTP_LOG_FLAG_WARN)
-#define HTTP_LOG_INFO    (httpLogLevel & HTTP_LOG_FLAG_INFO)
-#define HTTP_LOG_VERBOSE (httpLogLevel & HTTP_LOG_FLAG_VERBOSE)
-#define HTTP_LOG_TRACE   (httpLogLevel & HTTP_LOG_FLAG_TRACE)
-
-// Configure asynchronous logging.
-// We follow the default configuration,
-// but we reserve a special macro to easily disable asynchronous logging for debugging purposes.
-
-#define HTTP_LOG_ASYNC_ENABLED   YES
-
-#define HTTP_LOG_ASYNC_ERROR   ( NO && HTTP_LOG_ASYNC_ENABLED)
-#define HTTP_LOG_ASYNC_WARN    (YES && HTTP_LOG_ASYNC_ENABLED)
-#define HTTP_LOG_ASYNC_INFO    (YES && HTTP_LOG_ASYNC_ENABLED)
-#define HTTP_LOG_ASYNC_VERBOSE (YES && HTTP_LOG_ASYNC_ENABLED)
-#define HTTP_LOG_ASYNC_TRACE   (YES && HTTP_LOG_ASYNC_ENABLED)
-
-// Define logging primitives.
-
-#define HTTPLogError(...) do {} while (0)
-
-#define HTTPLogWarn(...) do {} while (0)
-
-#define HTTPLogInfo(...) do {} while (0)
-
-#define HTTPLogVerbose(...) do {} while (0)
-
-#define HTTPLogTrace() do {} while (0)
-
-#define HTTPLogTrace2(...) do {} while (0)
-
-
-#define HTTPLogCError(...) do {} while (0)
-
-#define HTTPLogCWarn(...) do {} while (0)
-
-#define HTTPLogCInfo(...) do {} while (0)
-
-#define HTTPLogCVerbose(...) do {} while (0)
-
-#define HTTPLogCTrace() do {} while (0)
-
-#define HTTPLogCTrace2(...) do {} while (0)
-

package/WebDriverAgentLib/Vendor/CocoaHTTPServer/HTTPMessage.h

@@ -1,53 +0,0 @@
-/**
- * The HTTPMessage class is a simple Objective-C wrapper for HTTP message parsing.
- * Migrated from CFHTTPMessage to use Foundation and Network framework.
- **/
-
-#import <Foundation/Foundation.h>
-
-#define HTTPVersion1_0  @"HTTP/1.0"
-#define HTTPVersion1_1  @"HTTP/1.1"
-
-
-@interface HTTPMessage : NSObject
-{
-  NSMutableDictionary *_headers;
-  NSMutableData *_body;
-  NSString *_version;
-  NSString *_method;
-  NSURL *_url;
-  NSInteger _statusCode;
-  NSString *_statusDescription;
-  BOOL _isRequest;
-  BOOL _headerComplete;
-  NSMutableData *_rawData;
-}
-
-- (id)initEmptyRequest;
-
-- (id)initRequestWithMethod:(NSString *)method URL:(NSURL *)url version:(NSString *)version;
-
-- (id)initResponseWithStatusCode:(NSInteger)code description:(NSString *)description version:(NSString *)version;
-
-- (BOOL)appendData:(NSData *)data;
-
-- (BOOL)isHeaderComplete;
-
-- (NSString *)version;
-
-- (NSString *)method;
-- (NSURL *)url;
-
-- (NSInteger)statusCode;
-
-- (NSDictionary *)allHeaderFields;
-- (NSString *)headerField:(NSString *)headerField;
-
-- (void)setHeaderField:(NSString *)headerField value:(NSString *)headerFieldValue;
-
-- (NSData *)messageData;
-
-- (NSData *)body;
-- (void)setBody:(NSData *)body;
-
-@end

package/WebDriverAgentLib/Vendor/CocoaHTTPServer/HTTPMessage.m

@@ -1,357 +0,0 @@
-#import "HTTPMessage.h"
-
-#if ! __has_feature(objc_arc)
-#warning This file must be compiled with ARC. Use -fobjc-arc flag (or convert project to ARC).
-#endif
-
-#pragma clang diagnostic ignored "-Wdirect-ivar-access"
-
-@implementation HTTPMessage
-
-- (id)init
-{
-  if ((self = [super init]))
-  {
-    _headers = [[NSMutableDictionary alloc] init];
-    _body = [[NSMutableData alloc] init];
-    _rawData = [[NSMutableData alloc] init];
-    _version = HTTPVersion1_1;
-    _headerComplete = NO;
-    _isRequest = YES;
-  }
-  return self;
-}
-
-- (id)initEmptyRequest
-{
-  if ((self = [self init]))
-  {
-    _isRequest = YES;
-  }
-  return self;
-}
-
-- (id)initRequestWithMethod:(NSString *)method URL:(NSURL *)url version:(NSString *)version
-{
-  if ((self = [self init]))
-  {
-    _isRequest = YES;
-    _method = [method copy];
-    _url = [url copy];
-    _version = version ? [version copy] : HTTPVersion1_1;
-  }
-  return self;
-}
-
-- (id)initResponseWithStatusCode:(NSInteger)code description:(NSString *)description version:(NSString *)version
-{
-  if ((self = [self init]))
-  {
-    _isRequest = NO;
-    _statusCode = code;
-    _statusDescription = [description copy];
-    _version = version ? [version copy] : HTTPVersion1_1;
-  }
-  return self;
-}
-
-- (BOOL)appendData:(NSData *)data
-{
-  if (!data || [data length] == 0)
-  {
-    return NO;
-  }
-
-  [_rawData appendData:data];
-
-  if (!_headerComplete)
-  {
-    // Look for the end of headers (CRLF CRLF or LF LF)
-    NSData *headerEndMarker = [@"\r\n\r\n" dataUsingEncoding:NSASCIIStringEncoding];
-    NSRange headerEndRange = [_rawData rangeOfData:headerEndMarker options:(NSDataSearchOptions)0 range:NSMakeRange(0, [_rawData length])];
-
-    if (headerEndRange.location == NSNotFound)
-    {
-      // Also check for LF LF (some clients use this)
-      NSData *lfMarker = [@"\n\n" dataUsingEncoding:NSASCIIStringEncoding];
-      headerEndRange = [_rawData rangeOfData:lfMarker options:(NSDataSearchOptions)0 range:NSMakeRange(0, [_rawData length])];
-    }
-
-    if (headerEndRange.location != NSNotFound)
-    {
-      _headerComplete = YES;
-
-      // Parse the header data
-      NSData *headerData = [_rawData subdataWithRange:NSMakeRange(0, headerEndRange.location + headerEndRange.length)];
-      NSString *headerString = [[NSString alloc] initWithData:headerData encoding:NSASCIIStringEncoding];
-
-      if (headerString)
-      {
-        [self parseHeaders:headerString];
-      }
-
-      // Extract body data if any
-      NSUInteger bodyStart = headerEndRange.location + headerEndRange.length;
-      if ([_rawData length] > bodyStart)
-      {
-        NSData *bodyData = [_rawData subdataWithRange:NSMakeRange(bodyStart, [_rawData length] - bodyStart)];
-        [_body appendData:bodyData];
-      }
-
-      [_rawData setLength:0];
-    }
-  }
-  else
-  {
-    // Headers are complete, append to body
-    [_body appendData:data];
-  }
-
-  return YES;
-}
-
-- (void)parseHeaders:(NSString *)headerString
-{
-  NSArray *lines;
-
-  // Try splitting by "\r\n" first (standard HTTP line ending)
-  // Check if the string actually contains "\r\n" delimiter
-  if ([headerString rangeOfString:@"\r\n"].location != NSNotFound)
-  {
-    // Found "\r\n" delimiter, use this split
-    lines = [headerString componentsSeparatedByString:@"\r\n"];
-  }
-  else
-  {
-    // No "\r\n" found, try "\n" (some clients use just LF)
-    lines = [headerString componentsSeparatedByString:@"\n"];
-  }
-
-  // componentsSeparatedByString: always returns at least one element,
-  // so check if we have meaningful content (non-empty first line)
-  if ([lines count] == 0 || [[lines objectAtIndex:0] length] == 0)
-  {
-    return;
-  }
-
-  // Parse first line (request line or status line)
-  NSString *firstLine = [lines objectAtIndex:0];
-  NSArray *firstLineParts = [firstLine componentsSeparatedByString:@" "];
-
-  if (_isRequest && [firstLineParts count] >= 3)
-  {
-    // Request line: METHOD URL VERSION
-    _method = [[firstLineParts objectAtIndex:0] copy];
-    NSString *urlString = [firstLineParts objectAtIndex:1];
-
-    // Handle both absolute URLs and relative paths
-    // Try absolute URL first
-    NSURL *parsedURL = [NSURL URLWithString:urlString];
-
-    // If that fails (nil), it's likely a relative path like "/endpoint"
-    // Create a URL with a base URL to handle relative paths
-    if (!parsedURL)
-    {
-      // Use a dummy base URL to allow relative path parsing
-      NSURL *baseURL = [NSURL URLWithString:@"http://localhost"];
-      parsedURL = [NSURL URLWithString:urlString relativeToURL:baseURL];
-    }
-
-    _url = [parsedURL copy];
-    if ([firstLineParts count] >= 3)
-    {
-      _version = [[firstLineParts objectAtIndex:2] copy];
-    }
-  }
-  else if (!_isRequest && [firstLineParts count] >= 3)
-  {
-    // Status line: VERSION CODE DESCRIPTION
-    _version = [[firstLineParts objectAtIndex:0] copy];
-    _statusCode = [[firstLineParts objectAtIndex:1] integerValue];
-    NSMutableArray *descParts = [NSMutableArray arrayWithArray:firstLineParts];
-    [descParts removeObjectAtIndex:0];
-    [descParts removeObjectAtIndex:0];
-    _statusDescription = [[descParts componentsJoinedByString:@" "] copy];
-  }
-
-  // Parse header fields
-  for (NSUInteger i = 1; i < [lines count]; i++)
-  {
-    NSString *line = [lines objectAtIndex:i];
-    if ([line length] == 0)
-    {
-      continue;
-    }
-
-    NSRange colonRange = [line rangeOfString:@":"];
-    if (colonRange.location != NSNotFound)
-    {
-      NSString *headerName = [[line substringToIndex:colonRange.location] stringByTrimmingCharactersInSet:[NSCharacterSet whitespaceCharacterSet]];
-      NSString *headerValue = [[line substringFromIndex:colonRange.location + 1] stringByTrimmingCharactersInSet:[NSCharacterSet whitespaceCharacterSet]];
-
-      if ([headerName length] > 0)
-      {
-        // HTTP headers are case-insensitive, but we'll store them with their original case
-        // For lookup, we'll use case-insensitive comparison
-        [_headers setObject:headerValue forKey:headerName];
-      }
-    }
-  }
-}
-
-- (BOOL)isHeaderComplete
-{
-  return _headerComplete;
-}
-
-- (NSString *)version
-{
-  return _version;
-}
-
-- (NSString *)method
-{
-  return _method;
-}
-
-- (NSURL *)url
-{
-  return _url;
-}
-
-- (NSInteger)statusCode
-{
-  return _statusCode;
-}
-
-- (NSDictionary *)allHeaderFields
-{
-  return [_headers copy];
-}
-
-- (NSString *)headerField:(NSString *)headerField
-{
-  // Case-insensitive lookup
-  for (NSString *key in [_headers allKeys])
-  {
-    if ([key caseInsensitiveCompare:headerField] == NSOrderedSame)
-    {
-      return [_headers objectForKey:key];
-    }
-  }
-  return nil;
-}
-
-- (void)setHeaderField:(NSString *)headerField value:(NSString *)headerFieldValue
-{
-  if (headerField && headerFieldValue)
-  {
-    // Remove existing header with same name (case-insensitive)
-    NSMutableArray *keysToRemove = [NSMutableArray array];
-    for (NSString *key in [_headers allKeys])
-    {
-      if ([key caseInsensitiveCompare:headerField] == NSOrderedSame)
-      {
-        [keysToRemove addObject:key];
-      }
-    }
-    [_headers removeObjectsForKeys:keysToRemove];
-
-    // Add new header
-    [_headers setObject:headerFieldValue forKey:headerField];
-  }
-}
-
-- (NSData *)messageData
-{
-  NSMutableString *messageString = [NSMutableString string];
-
-  if (_isRequest)
-  {
-    // Request line
-    // For relative URLs, use the path component; for absolute URLs, use absoluteString
-    NSString *urlString = nil;
-    if (_url)
-    {
-      // If it's a relative URL (has a base), use the relative path
-      // Otherwise use absoluteString or path
-      if ([_url baseURL])
-      {
-        // Relative URL - use the relative portion
-        urlString = [_url relativeString];
-      }
-      else
-      {
-        // Absolute URL
-        urlString = [_url absoluteString];
-        if (!urlString)
-        {
-          urlString = [_url path];
-        }
-      }
-    }
-    [messageString appendFormat:@"%@ %@ %@\r\n", _method ?: @"GET", urlString ?: @"/", _version ?: HTTPVersion1_1];
-  }
-  else
-  {
-    // Status line
-    [messageString appendFormat:@"%@ %ld %@\r\n", _version ?: HTTPVersion1_1, (long)_statusCode, _statusDescription ?: @""];
-  }
-
-  // Headers
-  for (NSString *key in [_headers allKeys])
-  {
-    NSString *value = [_headers objectForKey:key];
-    [messageString appendFormat:@"%@: %@\r\n", key, value];
-  }
-
-  // Empty line to separate headers from body
-  [messageString appendString:@"\r\n"];
-
-  NSMutableData *data = [NSMutableData dataWithData:(id)[messageString dataUsingEncoding:NSASCIIStringEncoding]];
-
-  // Append body if present
-  if ([_body length] > 0)
-  {
-    [data appendData:_body];
-  }
-
-  return data;
-}
-
-- (NSData *)body
-{
-  return [_body copy];
-}
-
-- (void)setBody:(NSData *)body
-{
-  if (body)
-  {
-    _body = [body mutableCopy];
-  }
-  else
-  {
-    _body = [[NSMutableData alloc] init];
-  }
-}
-
-- (void)dealloc
-{
-  // ARC automatically releases all instance variables, but we include this
-  // for clarity and to match the pattern of the original CFNetwork implementation.
-  // All Objective-C objects (_headers, _body, _rawData, _version, _method, _url, _statusDescription)
-  // will be automatically released by ARC when this object is deallocated.
-#if ! __has_feature(objc_arc)
-  [_headers release];
-  [_body release];
-  [_rawData release];
-  [_version release];
-  [_method release];
-  [_url release];
-  [_statusDescription release];
-  [super dealloc];
-#endif
-}
-
-@end

package/WebDriverAgentLib/Vendor/CocoaHTTPServer/HTTPResponse.h

@@ -1,149 +0,0 @@
-#import <Foundation/Foundation.h>
-
-
-@protocol HTTPResponse
-
-/**
- * Returns the length of the data in bytes.
- * If you don't know the length in advance, implement the isChunked method and have it return YES.
- **/
-- (UInt64)contentLength;
-
-/**
- * The HTTP server supports range requests in order to allow things like
- * file download resumption and optimized streaming on mobile devices.
- **/
-- (UInt64)offset;
-- (void)setOffset:(UInt64)offset;
-
-/**
- * Returns the data for the response.
- * You do not have to return data of the exact length that is given.
- * You may optionally return data of a lesser length.
- * However, you must never return data of a greater length than requested.
- * Doing so could disrupt proper support for range requests.
- * 
- * To support asynchronous responses, read the discussion at the bottom of this header.
- **/
-- (NSData *)readDataOfLength:(NSUInteger)length;
-
-/**
- * Should only return YES after the HTTPConnection has read all available data.
- * That is, all data for the response has been returned to the HTTPConnection via the readDataOfLength method.
- **/
-- (BOOL)isDone;
-
-@optional
-
-/**
- * If you need time to calculate any part of the HTTP response headers (status code or header fields),
- * this method allows you to delay sending the headers so that you may asynchronously execute the calculations.
- * Simply implement this method and return YES until you have everything you need concerning the headers.
- * 
- * This method ties into the asynchronous response architecture of the HTTPConnection.
- * You should read the full discussion at the bottom of this header.
- * 
- * If you return YES from this method,
- * the HTTPConnection will wait for you to invoke the responseHasAvailableData method.
- * After you do, the HTTPConnection will again invoke this method to see if the response is ready to send the headers.
- * 
- * You should only delay sending the headers until you have everything you need concerning just the headers.
- * Asynchronously generating the body of the response is not an excuse to delay sending the headers.
- * Instead you should tie into the asynchronous response architecture, and use techniques such as the isChunked method.
- * 
- * Important: You should read the discussion at the bottom of this header.
- **/
-- (BOOL)delayResponseHeaders;
-
-/**
- * Status code for response.
- * Allows for responses such as redirect (301), etc.
- **/
-- (NSInteger)status;
-
-/**
- * If you want to add any extra HTTP headers to the response,
- * simply return them in a dictionary in this method.
- **/
-- (NSDictionary *)httpHeaders;
-
-/**
- * If you don't know the content-length in advance,
- * implement this method in your custom response class and return YES.
- * 
- * Important: You should read the discussion at the bottom of this header.
- **/
-- (BOOL)isChunked;
-
-/**
- * This method is called from the HTTPConnection class when the connection is closed,
- * or when the connection is finished with the response.
- * If your response is asynchronous, you should implement this method so you know not to
- * invoke any methods on the HTTPConnection after this method is called (as the connection may be deallocated).
- **/
-- (void)connectionDidClose;
-
-@end
-
-
-/**
- * Important notice to those implementing custom asynchronous and/or chunked responses:
- * 
- * HTTPConnection supports asynchronous responses.  All you have to do in your custom response class is
- * asynchronously generate the response, and invoke HTTPConnection's responseHasAvailableData method.
- * You don't have to wait until you have all of the response ready to invoke this method.  For example, if you
- * generate the response in incremental chunks, you could call responseHasAvailableData after generating
- * each chunk.  Please see the HTTPAsyncFileResponse class for an example of how to do this.
- * 
- * The normal flow of events for an HTTPConnection while responding to a request is like this:
- *  - Send http resopnse headers
- *  - Get data from response via readDataOfLength method.
- *  - Add data to asyncSocket's write queue.
- *  - Wait for asyncSocket to notify it that the data has been sent.
- *  - Get more data from response via readDataOfLength method.
- *  - ... continue this cycle until the entire response has been sent.
- * 
- * With an asynchronous response, the flow is a little different.
- * 
- * First the HTTPResponse is given the opportunity to postpone sending the HTTP response headers.
- * This allows the response to asynchronously execute any code needed to calculate a part of the header.
- * An example might be the response needs to generate some custom header fields,
- * or perhaps the response needs to look for a resource on network-attached storage.
- * Since the network-attached storage may be slow, the response doesn't know whether to send a 200 or 404 yet.
- * In situations such as this, the HTTPResponse simply implements the delayResponseHeaders method and returns YES.
- * After returning YES from this method, the HTTPConnection will wait until the response invokes its
- * responseHasAvailableData method. After this occurs, the HTTPConnection will again query the delayResponseHeaders
- * method to see if the response is ready to send the headers.
- * This cycle will continue until the delayResponseHeaders method returns NO.
- * 
- * You should only delay sending the response headers until you have everything you need concerning just the headers.
- * Asynchronously generating the body of the response is not an excuse to delay sending the headers.
- * 
- * After the response headers have been sent, the HTTPConnection calls your readDataOfLength method.
- * You may or may not have any available data at this point. If you don't, then simply return nil.
- * You should later invoke HTTPConnection's responseHasAvailableData when you have data to send.
- * 
- * You don't have to keep track of when you return nil in the readDataOfLength method, or how many times you've invoked
- * responseHasAvailableData. Just simply call responseHasAvailableData whenever you've generated new data, and
- * return nil in your readDataOfLength whenever you don't have any available data in the requested range.
- * HTTPConnection will automatically detect when it should be requesting new data and will act appropriately.
- * 
- * It's important that you also keep in mind that the HTTP server supports range requests.
- * The setOffset method is mandatory, and should not be ignored.
- * Make sure you take into account the offset within the readDataOfLength method.
- * You should also be aware that the HTTPConnection automatically sorts any range requests.
- * So if your setOffset method is called with a value of 100, then you can safely release bytes 0-99.
- * 
- * HTTPConnection can also help you keep your memory footprint small.
- * Imagine you're dynamically generating a 10 MB response.  You probably don't want to load all this data into
- * RAM, and sit around waiting for HTTPConnection to slowly send it out over the network.  All you need to do
- * is pay attention to when HTTPConnection requests more data via readDataOfLength.  This is because HTTPConnection
- * will never allow asyncSocket's write queue to get much bigger than READ_CHUNKSIZE bytes.  You should
- * consider how you might be able to take advantage of this fact to generate your asynchronous response on demand,
- * while at the same time keeping your memory footprint small, and your application lightning fast.
- * 
- * If you don't know the content-length in advanced, you should also implement the isChunked method.
- * This means the response will not include a Content-Length header, and will instead use "Transfer-Encoding: chunked".
- * There's a good chance that if your response is asynchronous and dynamic, it's also chunked.
- * If your response is chunked, you don't need to worry about range requests.
- **/