/frameworks/base/docs/html/guide/topics/connectivity/ |
D | index.jd | 14 <h4>Android’s HTTP Clients</h4> 15 <p>Most network-connected Android apps will use HTTP to send and receive data. Android 16 includes two HTTP clients: HttpURLConnection and Apache HTTP Client. Both support HTTPS, streaming
|
/frameworks/volley/src/com/android/volley/toolbox/ |
D | HttpHeaderParser.java | 24 import org.apache.http.protocol.HTTP; 122 String contentType = headers.get(HTTP.CONTENT_TYPE); in parseCharset() 135 return HTTP.DEFAULT_CONTENT_CHARSET; in parseCharset()
|
/frameworks/base/core/java/android/net/http/ |
D | CharArrayBuffers.java | 20 import org.apache.http.protocol.HTTP; 43 while (beginIndex < len && HTTP.isWhitespace(chars[beginIndex])) { in containsIgnoreCaseTrimmed()
|
D | Headers.java | 27 import org.apache.http.protocol.HTTP; 186 if (HTTP.IDENTITY_CODING.equalsIgnoreCase(val)) { in parseHeader() 189 && (HTTP.CHUNK_CODING in parseHeader() 463 buffer, pos, HTTP.CONN_CLOSE)) { in setConnectionType() 466 buffer, pos, HTTP.CONN_KEEP_ALIVE)) { in setConnectionType()
|
/frameworks/base/docs/html/google/gcm/ |
D | server-ref.jd | 22 <li><a href="#error-codes">Downstream message error response codes (HTTP and XMPP)</a></li> 36 <li><a href="#error-codes">Downstream message error response codes (HTTP and XMPP)</a></li> 57 these messages can be either HTTP or XMPP. For plain text, these messages can only be HTTP.</p> 59 <h4>Downstream HTTP or XMPP messages (JSON)</h4> 61 <p>The following table lists the targets, options, and payload for HTTP or XMPP JSON messages.</p> 63 …<strong>Table 1.</strong> Targets, options, and payload for downstream HTTP or XMPP message (JSON)… 80 …s used in XMPP in place of {@code registration_ids} or {@code notification_key} in HTTP.</p></td> 84 <td>HTTP</td> 88 …<p>Multicast messages (sending to more than 1 registration IDs) are allowed using HTTP JSON format… 89 …<p>This parameter or {@code notification_key} is used in HTTP in place of {@code to} in XMPP.</p><… [all …]
|
D | http.jd | 1 page.title=GCM HTTP Connection Server 20 <li><a href="#app-server">Implementing an HTTP-Based App Server</a> 37 <p>This document describes the Google Cloud Messaging (GCM) HTTP 55 <p>A message request is made of 2 parts: HTTP header and HTTP body.</p> 57 <p>The HTTP header must contain the following headers:</p> 81 <p>The HTTP body content depends on whether you're using JSON or plain text. 154 <li>The message is processed successfully. The HTTP response has a 200 status, and 156 <li>The GCM server rejects the request. The HTTP response contains a 161 <p>When a JSON request is successful (HTTP status code 200), the response body 236 <p>When a plain-text request is successful (HTTP status code 200), the response [all …]
|
D | server.jd | 43 <li><a href="http.html">HTTP Connection Server</a></li> 59 HTTP</a> and <a href="{@docRoot}google/gcm/ccs.html">XMPP (CCS)</a> (XMPP).</li> 81 <li>Able to store the API key and client registration IDs. In HTTP, the API key is 98 <li>If you decide to use the HTTP connection server, you can use the 114 HTTP</a> and <a href="{@docRoot}google/gcm/ccs.html">XMPP (CCS)</a>. You can use them 115 separately or in tandem. XMPP (CCS) messaging differs from HTTP messaging in the following ways:</p> 119 <li>HTTP: Downstream only, cloud-to-device up to 4KB of data. </li> 126 <li>HTTP: Synchronous. 3rd-party app servers send messages as HTTP POST requests and 138 <li>HTTP: JSON messages sent as HTTP POST.</li> 144 <li>HTTP: Plain Text messages sent as HTTP POST.</li> [all …]
|
D | notifications.jd | 73 <a href="http.html">HTTP</a> connection server.</p> 117 <p>Here is the HTTP request header you should use for all server side create/add/remove operations:… 197 <p>Here is the HTTP request header you should use for all add/remove operations. The 273 <pre>HTTP status: 200 306 <p>In the case of failure, the response has HTTP code 503 and no JSON. When a message
|
D | client.jd | 182 <a href="ccs.html">CCS</a> (XMPP) server; HTTP-based servers don't support upstream messaging.</li> 402 // You should send the registration ID to your server over HTTP, 403 // so it can use GCM/HTTP or CCS to send messages to your app. 434 * Sends the registration ID to your server over HTTP, so it can use GCM/HTTP
|
/frameworks/base/obex/javax/obex/ |
D | HeaderSet.java | 118 public static final int HTTP = 0x47; field in HeaderSet 347 case HTTP: in setHeader() 486 case HTTP: in getHeader() 556 out.write(HTTP); in getHeaderList()
|
D | ObexHelper.java | 541 value = (byte[])headImpl.getHeader(HeaderSet.HTTP); in createHeader() 543 out.write((byte)HeaderSet.HTTP); in createHeader() 550 headImpl.setHeader(HeaderSet.HTTP, null); in createHeader()
|
/frameworks/base/docs/html/training/efficient-downloads/ |
D | redundant_redundant.jd | 38 … requested content was last updated, and when it expires, from within the HTTP response headers. T… 69 <p>Android 4.0 added a response cache to {@code HttpURLConnection}. You can enable HTTP response ca… 79 Log.d(TAG, "HTTP response cache is unavailable."); 85 <p>With the cache installed, fully cached HTTP requests can be served directly from local storage, …
|
/frameworks/base/core/java/com/android/internal/http/multipart/ |
D | MultipartEntity.java | 44 import org.apache.http.protocol.HTTP; 206 return new BasicHeader(HTTP.CONTENT_TYPE, buffer.toString()); in getContentType()
|
/frameworks/base/docs/html/training/basics/network-ops/ |
D | connecting.jd | 18 <li><a href="#http-client">Choose an HTTP Client</a></li> 50 <h2 id="http-client">Choose an HTTP Client</h2> 52 <p>Most network-connected Android apps use HTTP to send and receive data. 53 Android includes two HTTP clients: {@link java.net.HttpURLConnection} and Apache 59 >Android's HTTP Clients</a>.</p> 253 <a href="http://www.w3.org/Protocols/HTTP/HTRESP.html">status code</a>. This is
|
D | index.jd | 57 for information on Volley, an HTTP library that makes networking for Android apps 70 <dd>Learn how to connect to the network, choose an HTTP client, and perform
|
/frameworks/base/docs/html/training/volley/ |
D | requestqueue.jd | 45 must be initialized with the HTTP client your app is using to connect to the network. 53 Android's HTTP Clients</a>. </li> 59 Android the device is running and choose the appropriate HTTP client, for example:</p> 82 // Set up the network to use HttpURLConnection as the HTTP client.
|
D | index.jd | 34 <p>Volley is an HTTP library that makes networking for Android apps easier and most importantly, 44 <li>Transparent disk and memory response caching with standard HTTP
|
/frameworks/base/tests/CoreTests/android/core/ |
D | TestEventHandler.java | 22 import org.apache.http.protocol.HTTP; 281 s = HTTP.CONN_CLOSE; in headers() 283 s = HTTP.CONN_KEEP_ALIVE; in headers()
|
/frameworks/av/media/libstagefright/codecs/common/include/ |
D | voIndex.h | 78 _MAKE_SOURCE_ID (0x120000, HTTP)
|
/frameworks/base/core/java/android/net/ |
D | PacProxySelector.java | 95 Proxy proxy = proxyFromHostPort(Type.HTTP, trimmed.substring(PROXY.length())); in parseResponse()
|
D | ProxyInfo.java | 250 proxy = new java.net.Proxy(java.net.Proxy.Type.HTTP, inetSocketAddress); in makeProxy()
|
/frameworks/base/docs/html/training/articles/ |
D | security-ssl.jd | 12 <li><a href="#HttpsExample">An HTTP Example</a></li> 122 <p>Yes, it really can be that simple. If you want to tailor the HTTP request, you can cast to 370 server for more than one hostname with HTTP, the web server can tell from the HTTP/1.1 request 372 HTTPS, because the server has to know which certificate to return before it sees the HTTP 380 HTTP Client does not, which is one of the many reasons we discourage its use. One workaround 381 if you need to support Android 2.2 (and older) or Apache HTTP Client is to set up an alternative 430 Sometimes apps need to use SSL separate from HTTP. For example, an email app might use SSL variants
|
/frameworks/base/docs/html/guide/appendix/ |
D | media-formats.jd | 41 <li>HTTP/HTTPS progressive streaming</li> 42 …<li>HTTP/HTTPS live streaming <a href="http://tools.ietf.org/html/draft-pantos-http-live-streaming… 387 <p style="margin-top: 2em">For video content that is streamed over HTTP or RTSP, there are addition…
|
/frameworks/base/docs/html/google/ |
D | google_toc.cs | 169 <span class="en">HTTP</span></a></li>
|
/frameworks/base/docs/html/google/auth/ |
D | http-auth.jd | 33 HTTP, the <a href= 38 <p>You can then use that token in your HTTP-based communications with Google API services 45 APIs that you need to access over HTTP. If you're instead using the <a 110 <p>To acquire the OAuth 2.0 token that will grant you access to Google APIs over HTTP, you need to 551 over HTTP (including how to use <a
|