![(please configure the [header_logo] section in trac.ini)](https://www.ietf.org/images/ietflogotrans.gif)
Changeset 2482
- Timestamp:
- Nov 10, 2013, 11:27:45 PM (6 years ago)
- File:
-
- 1 edited
-
draft-ietf-httpbis/latest/p2-semantics.xml (modified) (11 diffs)
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.xml
r2481 r2482 2653 2653 <t> 2654 2654 Responses with status codes that are defined as cacheable by default 2655 (e.g., 200, 203, 20 6, 300, 301, and 410 in this specification) can be2656 reused by a cache with heuristic expiration unless otherwise indicated by2657 the method definition or explicit cache controls &caching;; all other2658 status codes are not cacheable by default.2655 (e.g., 200, 203, 204, 300, 301, 404, 405, 410, 414, 501 in this 2656 specification) can be reused by a cache with heuristic expiration unless 2657 otherwise indicated by the method definition or explicit cache controls 2658 &caching;; all other status codes are not cacheable by default. 2659 2659 </t> 2660 2660 <texttable align="left"> … … 2839 2839 </t> 2840 2840 <t> 2841 A 200 response is cacheable unless otherwise indicated by2841 A 200 response is cacheable by default; i.e., unless otherwise indicated by 2842 2842 the method definition or explicit cache controls (see &p6-heuristic;). 2843 2843 </t> … … 2904 2904 </t> 2905 2905 <t> 2906 A 203 response is cacheable unless otherwise indicated by2906 A 203 response is cacheable by default; i.e., unless otherwise indicated by 2907 2907 the method definition or explicit cache controls (see &p6-heuristic;). 2908 2908 </t> … … 2946 2946 </t> 2947 2947 <t> 2948 A 204 response is cacheable unless otherwise indicated by2948 A 204 response is cacheable by default; i.e., unless otherwise indicated by 2949 2949 the method definition or explicit cache controls (see &p6-heuristic;). 2950 2950 </t> … … 3093 3093 </t> 3094 3094 <t> 3095 A 300 response is cacheable unless otherwise indicated by3095 A 300 response is cacheable by default; i.e., unless otherwise indicated by 3096 3096 the method definition or explicit cache controls (see &p6-heuristic;). 3097 3097 </t> … … 3138 3138 </x:note> 3139 3139 <t> 3140 A 301 response is cacheable unless otherwise indicated by3140 A 301 response is cacheable by default; i.e., unless otherwise indicated by 3141 3141 the method definition or explicit cache controls (see &p6-heuristic;). 3142 3142 </t> … … 3332 3332 </t> 3333 3333 <t> 3334 A 404 response is cacheable unless otherwise indicated by3334 A 404 response is cacheable by default; i.e., unless otherwise indicated by 3335 3335 the method definition or explicit cache controls (see &p6-heuristic;). 3336 3336 </t> … … 3349 3349 </t> 3350 3350 <t> 3351 A 405 response is cacheable unless otherwise indicated by3351 A 405 response is cacheable by default; i.e., unless otherwise indicated by 3352 3352 the method definition or explicit cache controls (see &p6-heuristic;). 3353 3353 </t> … … 3436 3436 </t> 3437 3437 <t> 3438 A 410 response is cacheable unless otherwise indicated by3438 A 410 response is cacheable by default; i.e., unless otherwise indicated by 3439 3439 the method definition or explicit cache controls (see &p6-heuristic;). 3440 3440 </t> … … 3486 3486 </t> 3487 3487 <t> 3488 A 414 response is cacheable unless otherwise indicated by3488 A 414 response is cacheable by default; i.e., unless otherwise indicated by 3489 3489 the method definition or explicit cache controls (see &p6-heuristic;). 3490 3490 </t> … … 3576 3576 </t> 3577 3577 <t> 3578 A 501 response is cacheable unless otherwise indicated by3578 A 501 response is cacheable by default; i.e., unless otherwise indicated by 3579 3579 the method definition or explicit cache controls (see &p6-heuristic;). 3580 3580 </t>
Note: See TracChangeset
for help on using the changeset viewer.
