History log of /frameworks/base/tests/CoreTests/android/core/HttpHeaderTest.java
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
eb0ced7a094df2c73e052a066535f4359b11a92d 16-Aug-2010 Henrik Baard <henrik.baard@sonyericsson.com> Error in compound cache-control header.

A cache control header containing both no-cache and max-age attribute does not
behave as expected.

Cache-Control: no-cache, max-age=200000

Will set expired to 20000ms seconds, ignoring the no-cache header. My
interpretation is that the no-cache header should not be ignored in
this case.

Change-Id: Iadd1900e4d2c6c0dacc6bb3e7b944cf78ca9b266
/frameworks/base/tests/CoreTests/android/core/HttpHeaderTest.java
c692e8c4da1c5e481ec8564839d47576e643f50c 13-Jul-2010 Henrik Baard <henrik.baard@sonyericsson.com> Make HTTP Header class handle multiple cache-control fields.

The HTTP specification states the following about the fields:
Multiple message-header fields with the same field-name MAY be present
in a message if and only if the entire field-value for that header field
is defined as a comma-separated list [i.e., #(values)]. It MUST be
possible to combine the multiple header fields into one "field-name:
field-value" pair, without changing the semantics of the message, by
appending each subsequent field-value to the first, each separated by a
comma. The order in which header fields with the same field-name are
received is therefore significant to the interpretation of the combined
field value, and thus a proxy MUST NOT change the order of these field
values when a message is forwarded.

Change-Id: I1a6fe5cc8f541f8e80d559641d270d09eac9d85c
/frameworks/base/tests/CoreTests/android/core/HttpHeaderTest.java