Changeset 2663


Ignore:
Timestamp:
May 9, 2014, 2:52:21 AM (6 years ago)
Author:
julian.reschke@…
Message:

min. fixes (reg names, punctuation, etc) (see #553)

Location:
draft-ietf-httpbis/latest
Files:
8 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/auth48/p1-messaging.unpg.txt

    r2661 r2663  
    66Obsoletes: 2145, 2616                                    J. Reschke, Ed.
    77(if approved)                                                 greenbytes
    8 Updates: 2817, 2818 (if approved)                            May 8, 2014
     8Updates: 2817, 2818 (if approved)                            May 9, 2014
    99Intended status: Standards Track
    10 Expires: November 9, 2014
     10Expires: November 10, 2014
    1111
    1212
     
    5353
    5454
    55 Fielding & Reschke      Expires November 9, 2014                [Page 1]
     55Fielding & Reschke      Expires November 10, 2014               [Page 1]
    5656
    5757
     
    6262   material or to cite them other than as "work in progress."
    6363
    64    This Internet-Draft will expire on November 9, 2014.
     64   This Internet-Draft will expire on November 10, 2014.
    6565
    6666Copyright Notice
     
    110110
    111111
    112 Fielding & Reschke      Expires November 9, 2014                [Page 2]
     112Fielding & Reschke      Expires November 10, 2014               [Page 2]
    113113
    114114
     
    167167
    168168
    169 Fielding & Reschke      Expires November 9, 2014                [Page 3]
     169Fielding & Reschke      Expires November 10, 2014               [Page 3]
    170170
    171171
     
    224224
    225225
    226 Fielding & Reschke      Expires November 9, 2014                [Page 4]
     226Fielding & Reschke      Expires November 10, 2014               [Page 4]
    227227
    228228
     
    281281
    282282
    283 Fielding & Reschke      Expires November 9, 2014                [Page 5]
     283Fielding & Reschke      Expires November 10, 2014               [Page 5]
    284284
    285285
     
    338338
    339339
    340 Fielding & Reschke      Expires November 9, 2014                [Page 6]
     340Fielding & Reschke      Expires November 10, 2014               [Page 6]
    341341
    342342
     
    395395
    396396
    397 Fielding & Reschke      Expires November 9, 2014                [Page 7]
     397Fielding & Reschke      Expires November 10, 2014               [Page 7]
    398398
    399399
     
    452452
    453453
    454 Fielding & Reschke      Expires November 9, 2014                [Page 8]
     454Fielding & Reschke      Expires November 10, 2014               [Page 8]
    455455
    456456
     
    509509
    510510
    511 Fielding & Reschke      Expires November 9, 2014                [Page 9]
     511Fielding & Reschke      Expires November 10, 2014               [Page 9]
    512512
    513513
     
    566566
    567567
    568 Fielding & Reschke      Expires November 9, 2014               [Page 10]
     568Fielding & Reschke      Expires November 10, 2014              [Page 10]
    569569
    570570
     
    623623
    624624
    625 Fielding & Reschke      Expires November 9, 2014               [Page 11]
     625Fielding & Reschke      Expires November 10, 2014              [Page 11]
    626626
    627627
     
    680680
    681681
    682 Fielding & Reschke      Expires November 9, 2014               [Page 12]
     682Fielding & Reschke      Expires November 10, 2014              [Page 12]
    683683
    684684
     
    737737
    738738
    739 Fielding & Reschke      Expires November 9, 2014               [Page 13]
     739Fielding & Reschke      Expires November 10, 2014              [Page 13]
    740740
    741741
     
    794794
    795795
    796 Fielding & Reschke      Expires November 9, 2014               [Page 14]
     796Fielding & Reschke      Expires November 10, 2014              [Page 14]
    797797
    798798
     
    851851
    852852
    853 Fielding & Reschke      Expires November 9, 2014               [Page 15]
     853Fielding & Reschke      Expires November 10, 2014              [Page 15]
    854854
    855855
     
    908908
    909909
    910 Fielding & Reschke      Expires November 9, 2014               [Page 16]
     910Fielding & Reschke      Expires November 10, 2014              [Page 16]
    911911
    912912
     
    965965
    966966
    967 Fielding & Reschke      Expires November 9, 2014               [Page 17]
     967Fielding & Reschke      Expires November 10, 2014              [Page 17]
    968968
    969969
     
    10221022
    10231023
    1024 Fielding & Reschke      Expires November 9, 2014               [Page 18]
     1024Fielding & Reschke      Expires November 10, 2014              [Page 18]
    10251025
    10261026
     
    10791079
    10801080
    1081 Fielding & Reschke      Expires November 9, 2014               [Page 19]
     1081Fielding & Reschke      Expires November 10, 2014              [Page 19]
    10821082
    10831083
     
    11361136
    11371137
    1138 Fielding & Reschke      Expires November 9, 2014               [Page 20]
     1138Fielding & Reschke      Expires November 10, 2014              [Page 20]
    11391139
    11401140
     
    11931193
    11941194
    1195 Fielding & Reschke      Expires November 9, 2014               [Page 21]
     1195Fielding & Reschke      Expires November 10, 2014              [Page 21]
    11961196
    11971197
     
    12501250
    12511251
    1252 Fielding & Reschke      Expires November 9, 2014               [Page 22]
     1252Fielding & Reschke      Expires November 10, 2014              [Page 22]
    12531253
    12541254
     
    13071307
    13081308
    1309 Fielding & Reschke      Expires November 9, 2014               [Page 23]
     1309Fielding & Reschke      Expires November 10, 2014              [Page 23]
    13101310
    13111311
     
    13641364
    13651365
    1366 Fielding & Reschke      Expires November 9, 2014               [Page 24]
     1366Fielding & Reschke      Expires November 10, 2014              [Page 24]
    13671367
    13681368
     
    14211421
    14221422
    1423 Fielding & Reschke      Expires November 9, 2014               [Page 25]
     1423Fielding & Reschke      Expires November 10, 2014              [Page 25]
    14241424
    14251425
     
    14781478
    14791479
    1480 Fielding & Reschke      Expires November 9, 2014               [Page 26]
     1480Fielding & Reschke      Expires November 10, 2014              [Page 26]
    14811481
    14821482
     
    15351535
    15361536
    1537 Fielding & Reschke      Expires November 9, 2014               [Page 27]
     1537Fielding & Reschke      Expires November 10, 2014              [Page 27]
    15381538
    15391539
     
    15921592
    15931593
    1594 Fielding & Reschke      Expires November 9, 2014               [Page 28]
     1594Fielding & Reschke      Expires November 10, 2014              [Page 28]
    15951595
    15961596
     
    16491649
    16501650
    1651 Fielding & Reschke      Expires November 9, 2014               [Page 29]
     1651Fielding & Reschke      Expires November 10, 2014              [Page 29]
    16521652
    16531653
     
    17061706
    17071707
    1708 Fielding & Reschke      Expires November 9, 2014               [Page 30]
     1708Fielding & Reschke      Expires November 10, 2014              [Page 30]
    17091709
    17101710
     
    17631763
    17641764
    1765 Fielding & Reschke      Expires November 9, 2014               [Page 31]
     1765Fielding & Reschke      Expires November 10, 2014              [Page 31]
    17661766
    17671767
     
    18201820
    18211821
    1822 Fielding & Reschke      Expires November 9, 2014               [Page 32]
     1822Fielding & Reschke      Expires November 10, 2014              [Page 32]
    18231823
    18241824
     
    18771877
    18781878
    1879 Fielding & Reschke      Expires November 9, 2014               [Page 33]
     1879Fielding & Reschke      Expires November 10, 2014              [Page 33]
    18801880
    18811881
     
    19341934
    19351935
    1936 Fielding & Reschke      Expires November 9, 2014               [Page 34]
     1936Fielding & Reschke      Expires November 10, 2014              [Page 34]
    19371937
    19381938
     
    19911991
    19921992
    1993 Fielding & Reschke      Expires November 9, 2014               [Page 35]
     1993Fielding & Reschke      Expires November 10, 2014              [Page 35]
    19941994
    19951995
     
    20482048
    20492049
    2050 Fielding & Reschke      Expires November 9, 2014               [Page 36]
     2050Fielding & Reschke      Expires November 10, 2014              [Page 36]
    20512051
    20522052
     
    21052105
    21062106
    2107 Fielding & Reschke      Expires November 9, 2014               [Page 37]
     2107Fielding & Reschke      Expires November 10, 2014              [Page 37]
    21082108
    21092109
     
    21622162
    21632163
    2164 Fielding & Reschke      Expires November 9, 2014               [Page 38]
     2164Fielding & Reschke      Expires November 10, 2014              [Page 38]
    21652165
    21662166
     
    22192219
    22202220
    2221 Fielding & Reschke      Expires November 9, 2014               [Page 39]
     2221Fielding & Reschke      Expires November 10, 2014              [Page 39]
    22222222
    22232223
     
    22762276
    22772277
    2278 Fielding & Reschke      Expires November 9, 2014               [Page 40]
     2278Fielding & Reschke      Expires November 10, 2014              [Page 40]
    22792279
    22802280
     
    23332333
    23342334
    2335 Fielding & Reschke      Expires November 9, 2014               [Page 41]
     2335Fielding & Reschke      Expires November 10, 2014              [Page 41]
    23362336
    23372337
     
    23902390
    23912391
    2392 Fielding & Reschke      Expires November 9, 2014               [Page 42]
     2392Fielding & Reschke      Expires November 10, 2014              [Page 42]
    23932393
    23942394
     
    24472447
    24482448
    2449 Fielding & Reschke      Expires November 9, 2014               [Page 43]
     2449Fielding & Reschke      Expires November 10, 2014              [Page 43]
    24502450
    24512451
     
    25042504
    25052505
    2506 Fielding & Reschke      Expires November 9, 2014               [Page 44]
     2506Fielding & Reschke      Expires November 10, 2014              [Page 44]
    25072507
    25082508
     
    25612561
    25622562
    2563 Fielding & Reschke      Expires November 9, 2014               [Page 45]
     2563Fielding & Reschke      Expires November 10, 2014              [Page 45]
    25642564
    25652565
     
    26182618
    26192619
    2620 Fielding & Reschke      Expires November 9, 2014               [Page 46]
     2620Fielding & Reschke      Expires November 10, 2014              [Page 46]
    26212621
    26222622
     
    26752675
    26762676
    2677 Fielding & Reschke      Expires November 9, 2014               [Page 47]
     2677Fielding & Reschke      Expires November 10, 2014              [Page 47]
    26782678
    26792679
     
    27322732
    27332733
    2734 Fielding & Reschke      Expires November 9, 2014               [Page 48]
     2734Fielding & Reschke      Expires November 10, 2014              [Page 48]
    27352735
    27362736
     
    27892789
    27902790
    2791 Fielding & Reschke      Expires November 9, 2014               [Page 49]
     2791Fielding & Reschke      Expires November 10, 2014              [Page 49]
    27922792
    27932793
     
    28462846
    28472847
    2848 Fielding & Reschke      Expires November 9, 2014               [Page 50]
     2848Fielding & Reschke      Expires November 10, 2014              [Page 50]
    28492849
    28502850
     
    29032903
    29042904
    2905 Fielding & Reschke      Expires November 9, 2014               [Page 51]
     2905Fielding & Reschke      Expires November 10, 2014              [Page 51]
    29062906
    29072907
     
    29602960
    29612961
    2962 Fielding & Reschke      Expires November 9, 2014               [Page 52]
     2962Fielding & Reschke      Expires November 10, 2014              [Page 52]
    29632963
    29642964
     
    30173017
    30183018
    3019 Fielding & Reschke      Expires November 9, 2014               [Page 53]
     3019Fielding & Reschke      Expires November 10, 2014              [Page 53]
    30203020
    30213021
     
    30743074
    30753075
    3076 Fielding & Reschke      Expires November 9, 2014               [Page 54]
     3076Fielding & Reschke      Expires November 10, 2014              [Page 54]
    30773077
    30783078
     
    31313131
    31323132
    3133 Fielding & Reschke      Expires November 9, 2014               [Page 55]
     3133Fielding & Reschke      Expires November 10, 2014              [Page 55]
    31343134
    31353135
     
    31883188
    31893189
    3190 Fielding & Reschke      Expires November 9, 2014               [Page 56]
     3190Fielding & Reschke      Expires November 10, 2014              [Page 56]
    31913191
    31923192
     
    32453245
    32463246
    3247 Fielding & Reschke      Expires November 9, 2014               [Page 57]
     3247Fielding & Reschke      Expires November 10, 2014              [Page 57]
    32483248
    32493249
     
    33023302
    33033303
    3304 Fielding & Reschke      Expires November 9, 2014               [Page 58]
     3304Fielding & Reschke      Expires November 10, 2014              [Page 58]
    33053305
    33063306
     
    33593359
    33603360
    3361 Fielding & Reschke      Expires November 9, 2014               [Page 59]
     3361Fielding & Reschke      Expires November 10, 2014              [Page 59]
    33623362
    33633363
     
    34163416
    34173417
    3418 Fielding & Reschke      Expires November 9, 2014               [Page 60]
     3418Fielding & Reschke      Expires November 10, 2014              [Page 60]
    34193419
    34203420
     
    34733473
    34743474
    3475 Fielding & Reschke      Expires November 9, 2014               [Page 61]
     3475Fielding & Reschke      Expires November 10, 2014              [Page 61]
    34763476
    34773477
     
    35303530
    35313531
    3532 Fielding & Reschke      Expires November 9, 2014               [Page 62]
     3532Fielding & Reschke      Expires November 10, 2014              [Page 62]
    35333533
    35343534
     
    35873587
    35883588
    3589 Fielding & Reschke      Expires November 9, 2014               [Page 63]
     3589Fielding & Reschke      Expires November 10, 2014              [Page 63]
    35903590
    35913591
     
    36443644
    36453645
    3646 Fielding & Reschke      Expires November 9, 2014               [Page 64]
     3646Fielding & Reschke      Expires November 10, 2014              [Page 64]
    36473647
    36483648
     
    37013701
    37023702
    3703 Fielding & Reschke      Expires November 9, 2014               [Page 65]
     3703Fielding & Reschke      Expires November 10, 2014              [Page 65]
    37043704
    37053705
     
    37583758
    37593759
    3760 Fielding & Reschke      Expires November 9, 2014               [Page 66]
     3760Fielding & Reschke      Expires November 10, 2014              [Page 66]
    37613761
    37623762
     
    38153815
    38163816
    3817 Fielding & Reschke      Expires November 9, 2014               [Page 67]
     3817Fielding & Reschke      Expires November 10, 2014              [Page 67]
    38183818
    38193819
     
    38723872
    38733873
    3874 Fielding & Reschke      Expires November 9, 2014               [Page 68]
     3874Fielding & Reschke      Expires November 10, 2014              [Page 68]
    38753875
    38763876
     
    39293929
    39303930
    3931 Fielding & Reschke      Expires November 9, 2014               [Page 69]
     3931Fielding & Reschke      Expires November 10, 2014              [Page 69]
    39323932
    39333933
     
    39863986
    39873987
    3988 Fielding & Reschke      Expires November 9, 2014               [Page 70]
     3988Fielding & Reschke      Expires November 10, 2014              [Page 70]
    39893989
    39903990
     
    40434043
    40444044
    4045 Fielding & Reschke      Expires November 9, 2014               [Page 71]
     4045Fielding & Reschke      Expires November 10, 2014              [Page 71]
    40464046
    40474047
     
    41004100
    41014101
    4102 Fielding & Reschke      Expires November 9, 2014               [Page 72]
     4102Fielding & Reschke      Expires November 10, 2014              [Page 72]
    41034103
    41044104
     
    41574157
    41584158
    4159 Fielding & Reschke      Expires November 9, 2014               [Page 73]
     4159Fielding & Reschke      Expires November 10, 2014              [Page 73]
    41604160
    41614161
     
    42144214
    42154215
    4216 Fielding & Reschke      Expires November 9, 2014               [Page 74]
     4216Fielding & Reschke      Expires November 10, 2014              [Page 74]
    42174217
    42184218
     
    42714271
    42724272
    4273 Fielding & Reschke      Expires November 9, 2014               [Page 75]
     4273Fielding & Reschke      Expires November 10, 2014              [Page 75]
    42744274
    42754275
     
    43284328
    43294329
    4330 Fielding & Reschke      Expires November 9, 2014               [Page 76]
     4330Fielding & Reschke      Expires November 10, 2014              [Page 76]
    43314331
    43324332
     
    43854385
    43864386
    4387 Fielding & Reschke      Expires November 9, 2014               [Page 77]
     4387Fielding & Reschke      Expires November 10, 2014              [Page 77]
    43884388
    43894389
     
    44424442
    44434443
    4444 Fielding & Reschke      Expires November 9, 2014               [Page 78]
     4444Fielding & Reschke      Expires November 10, 2014              [Page 78]
    44454445
    44464446
     
    44994499
    45004500
    4501 Fielding & Reschke      Expires November 9, 2014               [Page 79]
     4501Fielding & Reschke      Expires November 10, 2014              [Page 79]
    45024502
    45034503
     
    45564556
    45574557
    4558 Fielding & Reschke      Expires November 9, 2014               [Page 80]
     4558Fielding & Reschke      Expires November 10, 2014              [Page 80]
    45594559
    45604560
     
    46134613
    46144614
    4615 Fielding & Reschke      Expires November 9, 2014               [Page 81]
     4615Fielding & Reschke      Expires November 10, 2014              [Page 81]
    46164616
    46174617
     
    46704670
    46714671
    4672 Fielding & Reschke      Expires November 9, 2014               [Page 82]
     4672Fielding & Reschke      Expires November 10, 2014              [Page 82]
    46734673
    46744674
     
    47274727
    47284728
    4729 Fielding & Reschke      Expires November 9, 2014               [Page 83]
     4729Fielding & Reschke      Expires November 10, 2014              [Page 83]
    47304730
    47314731
     
    47844784
    47854785
    4786 Fielding & Reschke      Expires November 9, 2014               [Page 84]
     4786Fielding & Reschke      Expires November 10, 2014              [Page 84]
    47874787
    47884788
     
    48414841
    48424842
    4843 Fielding & Reschke      Expires November 9, 2014               [Page 85]
     4843Fielding & Reschke      Expires November 10, 2014              [Page 85]
    48444844
    48454845
     
    48984898
    48994899
    4900 Fielding & Reschke      Expires November 9, 2014               [Page 86]
    4901 
    4902 
     4900Fielding & Reschke      Expires November 10, 2014              [Page 86]
     4901
     4902
  • draft-ietf-httpbis/latest/auth48/p2-semantics.unpg.txt

    r2660 r2663  
    66Obsoletes: 2616 (if approved)                            J. Reschke, Ed.
    77Updates: 2817 (if approved)                                   greenbytes
    8 Intended status: Standards Track                             May 8, 2014
    9 Expires: November 9, 2014
     8Intended status: Standards Track                             May 9, 2014
     9Expires: November 10, 2014
    1010
    1111
     
    5353
    5454
    55 Fielding & Reschke      Expires November 9, 2014                [Page 1]
     55Fielding & Reschke      Expires November 10, 2014               [Page 1]
    5656
    5757
     
    6161   material or to cite them other than as "work in progress."
    6262
    63    This Internet-Draft will expire on November 9, 2014.
     63   This Internet-Draft will expire on November 10, 2014.
    6464
    6565Copyright Notice
     
    110110
    111111
    112 Fielding & Reschke      Expires November 9, 2014                [Page 2]
     112Fielding & Reschke      Expires November 10, 2014               [Page 2]
    113113
    114114
     
    167167
    168168
    169 Fielding & Reschke      Expires November 9, 2014                [Page 3]
     169Fielding & Reschke      Expires November 10, 2014               [Page 3]
    170170
    171171
     
    224224
    225225
    226 Fielding & Reschke      Expires November 9, 2014                [Page 4]
     226Fielding & Reschke      Expires November 10, 2014               [Page 4]
    227227
    228228
     
    281281
    282282
    283 Fielding & Reschke      Expires November 9, 2014                [Page 5]
     283Fielding & Reschke      Expires November 10, 2014               [Page 5]
    284284
    285285
     
    338338
    339339
    340 Fielding & Reschke      Expires November 9, 2014                [Page 6]
     340Fielding & Reschke      Expires November 10, 2014               [Page 6]
    341341
    342342
     
    3503502.  Resources
    351351
    352    The target of an HTTP request is called a resource.  HTTP does not
     352   The target of an HTTP request is called a "resource".  HTTP does not
    353353   limit the nature of a resource; it merely defines an interface that
    354354   might be used to interact with resources.  Each resource is
     
    395395
    396396
    397 Fielding & Reschke      Expires November 9, 2014                [Page 7]
     397Fielding & Reschke      Expires November 10, 2014               [Page 7]
    398398
    399399
     
    4294293.1.1.1.  Media Type
    430430
    431    HTTP uses Internet Media Types [RFC2046] in the Content-Type
     431   HTTP uses Internet media types [RFC2046] in the Content-Type
    432432   (Section 3.1.1.5) and Accept (Section 5.3.2) header fields in order
    433433   to provide open and extensible data typing and type negotiation.
     
    452452
    453453
    454 Fielding & Reschke      Expires November 9, 2014                [Page 8]
     454Fielding & Reschke      Expires November 10, 2014               [Page 8]
    455455
    456456
     
    486486     charset = token
    487487
    488    Charset names ought to be registered in the IANA Character Set
     488   Charset names ought to be registered in the IANA "Character Sets"
    489489   registry (<http://www.iana.org/assignments/character-sets>) according
    490490   to the procedures defined in [RFC2978].
     
    509509
    510510
    511 Fielding & Reschke      Expires November 9, 2014                [Page 9]
     511Fielding & Reschke      Expires November 10, 2014               [Page 9]
    512512
    513513
     
    566566
    567567
    568 Fielding & Reschke      Expires November 9, 2014               [Page 10]
     568Fielding & Reschke      Expires November 10, 2014              [Page 10]
    569569
    570570
     
    623623
    624624
    625 Fielding & Reschke      Expires November 9, 2014               [Page 11]
     625Fielding & Reschke      Expires November 10, 2014              [Page 11]
    626626
    627627
     
    680680
    681681
    682 Fielding & Reschke      Expires November 9, 2014               [Page 12]
     682Fielding & Reschke      Expires November 10, 2014              [Page 12]
    683683
    684684
     
    737737
    738738
    739 Fielding & Reschke      Expires November 9, 2014               [Page 13]
     739Fielding & Reschke      Expires November 10, 2014              [Page 13]
    740740
    741741
     
    794794
    795795
    796 Fielding & Reschke      Expires November 9, 2014               [Page 14]
     796Fielding & Reschke      Expires November 10, 2014              [Page 14]
    797797
    798798
     
    851851
    852852
    853 Fielding & Reschke      Expires November 9, 2014               [Page 15]
     853Fielding & Reschke      Expires November 10, 2014              [Page 15]
    854854
    855855
     
    908908
    909909
    910 Fielding & Reschke      Expires November 9, 2014               [Page 16]
     910Fielding & Reschke      Expires November 10, 2014              [Page 16]
    911911
    912912
     
    965965
    966966
    967 Fielding & Reschke      Expires November 9, 2014               [Page 17]
     967Fielding & Reschke      Expires November 10, 2014              [Page 17]
    968968
    969969
     
    10221022
    10231023
    1024 Fielding & Reschke      Expires November 9, 2014               [Page 18]
     1024Fielding & Reschke      Expires November 10, 2014              [Page 18]
    10251025
    10261026
     
    10791079
    10801080
    1081 Fielding & Reschke      Expires November 9, 2014               [Page 19]
     1081Fielding & Reschke      Expires November 10, 2014              [Page 19]
    10821082
    10831083
     
    11361136
    11371137
    1138 Fielding & Reschke      Expires November 9, 2014               [Page 20]
     1138Fielding & Reschke      Expires November 10, 2014              [Page 20]
    11391139
    11401140
     
    11931193
    11941194
    1195 Fielding & Reschke      Expires November 9, 2014               [Page 21]
     1195Fielding & Reschke      Expires November 10, 2014              [Page 21]
    11961196
    11971197
     
    12501250
    12511251
    1252 Fielding & Reschke      Expires November 9, 2014               [Page 22]
     1252Fielding & Reschke      Expires November 10, 2014              [Page 22]
    12531253
    12541254
     
    13071307
    13081308
    1309 Fielding & Reschke      Expires November 9, 2014               [Page 23]
     1309Fielding & Reschke      Expires November 10, 2014              [Page 23]
    13101310
    13111311
     
    13641364
    13651365
    1366 Fielding & Reschke      Expires November 9, 2014               [Page 24]
     1366Fielding & Reschke      Expires November 10, 2014              [Page 24]
    13671367
    13681368
     
    14211421
    14221422
    1423 Fielding & Reschke      Expires November 9, 2014               [Page 25]
     1423Fielding & Reschke      Expires November 10, 2014              [Page 25]
    14241424
    14251425
     
    14781478
    14791479
    1480 Fielding & Reschke      Expires November 9, 2014               [Page 26]
     1480Fielding & Reschke      Expires November 10, 2014              [Page 26]
    14811481
    14821482
     
    15351535
    15361536
    1537 Fielding & Reschke      Expires November 9, 2014               [Page 27]
     1537Fielding & Reschke      Expires November 10, 2014              [Page 27]
    15381538
    15391539
     
    15921592
    15931593
    1594 Fielding & Reschke      Expires November 9, 2014               [Page 28]
     1594Fielding & Reschke      Expires November 10, 2014              [Page 28]
    15951595
    15961596
     
    16491649
    16501650
    1651 Fielding & Reschke      Expires November 9, 2014               [Page 29]
     1651Fielding & Reschke      Expires November 10, 2014              [Page 29]
    16521652
    16531653
     
    17061706
    17071707
    1708 Fielding & Reschke      Expires November 9, 2014               [Page 30]
     1708Fielding & Reschke      Expires November 10, 2014              [Page 30]
    17091709
    17101710
     
    17631763
    17641764
    1765 Fielding & Reschke      Expires November 9, 2014               [Page 31]
     1765Fielding & Reschke      Expires November 10, 2014              [Page 31]
    17661766
    17671767
     
    18201820
    18211821
    1822 Fielding & Reschke      Expires November 9, 2014               [Page 32]
     1822Fielding & Reschke      Expires November 10, 2014              [Page 32]
    18231823
    18241824
     
    18771877
    18781878
    1879 Fielding & Reschke      Expires November 9, 2014               [Page 33]
     1879Fielding & Reschke      Expires November 10, 2014              [Page 33]
    18801880
    18811881
     
    19341934
    19351935
    1936 Fielding & Reschke      Expires November 9, 2014               [Page 34]
     1936Fielding & Reschke      Expires November 10, 2014              [Page 34]
    19371937
    19381938
     
    19911991
    19921992
    1993 Fielding & Reschke      Expires November 9, 2014               [Page 35]
     1993Fielding & Reschke      Expires November 10, 2014              [Page 35]
    19941994
    19951995
     
    20482048
    20492049
    2050 Fielding & Reschke      Expires November 9, 2014               [Page 36]
     2050Fielding & Reschke      Expires November 10, 2014              [Page 36]
    20512051
    20522052
     
    21052105
    21062106
    2107 Fielding & Reschke      Expires November 9, 2014               [Page 37]
     2107Fielding & Reschke      Expires November 10, 2014              [Page 37]
    21082108
    21092109
     
    21622162
    21632163
    2164 Fielding & Reschke      Expires November 9, 2014               [Page 38]
     2164Fielding & Reschke      Expires November 10, 2014              [Page 38]
    21652165
    21662166
     
    22192219
    22202220
    2221 Fielding & Reschke      Expires November 9, 2014               [Page 39]
     2221Fielding & Reschke      Expires November 10, 2014              [Page 39]
    22222222
    22232223
     
    22762276
    22772277
    2278 Fielding & Reschke      Expires November 9, 2014               [Page 40]
     2278Fielding & Reschke      Expires November 10, 2014              [Page 40]
    22792279
    22802280
     
    23332333
    23342334
    2335 Fielding & Reschke      Expires November 9, 2014               [Page 41]
     2335Fielding & Reschke      Expires November 10, 2014              [Page 41]
    23362336
    23372337
     
    23902390
    23912391
    2392 Fielding & Reschke      Expires November 9, 2014               [Page 42]
     2392Fielding & Reschke      Expires November 10, 2014              [Page 42]
    23932393
    23942394
     
    24472447
    24482448
    2449 Fielding & Reschke      Expires November 9, 2014               [Page 43]
     2449Fielding & Reschke      Expires November 10, 2014              [Page 43]
    24502450
    24512451
     
    25042504
    25052505
    2506 Fielding & Reschke      Expires November 9, 2014               [Page 44]
     2506Fielding & Reschke      Expires November 10, 2014              [Page 44]
    25072507
    25082508
     
    25372537   If the target URI was obtained from a source that does not have its
    25382538   own URI (e.g., input from the user keyboard, or an entry within the
    2539    user's bookmarks/favorites), the user agent MUST either exclude
    2540    Referer or send it with a value of "about:blank".
     2539   user's bookmarks/favorites), the user agent MUST either exclude the
     2540   Referer field or send it with a value of "about:blank".
    25412541
    25422542   The Referer field has the potential to reveal information about the
     
    25612561
    25622562
    2563 Fielding & Reschke      Expires November 9, 2014               [Page 45]
     2563Fielding & Reschke      Expires November 10, 2014              [Page 45]
    25642564
    25652565
     
    26182618
    26192619
    2620 Fielding & Reschke      Expires November 9, 2014               [Page 46]
     2620Fielding & Reschke      Expires November 10, 2014              [Page 46]
    26212621
    26222622
     
    26752675
    26762676
    2677 Fielding & Reschke      Expires November 9, 2014               [Page 47]
     2677Fielding & Reschke      Expires November 10, 2014              [Page 47]
    26782678
    26792679
     
    27322732
    27332733
    2734 Fielding & Reschke      Expires November 9, 2014               [Page 48]
     2734Fielding & Reschke      Expires November 10, 2014              [Page 48]
    27352735
    27362736
     
    27892789
    27902790
    2791 Fielding & Reschke      Expires November 9, 2014               [Page 49]
     2791Fielding & Reschke      Expires November 10, 2014              [Page 49]
    27922792
    27932793
     
    28462846
    28472847
    2848 Fielding & Reschke      Expires November 9, 2014               [Page 50]
     2848Fielding & Reschke      Expires November 10, 2014              [Page 50]
    28492849
    28502850
     
    29032903
    29042904
    2905 Fielding & Reschke      Expires November 9, 2014               [Page 51]
     2905Fielding & Reschke      Expires November 10, 2014              [Page 51]
    29062906
    29072907
     
    29602960
    29612961
    2962 Fielding & Reschke      Expires November 9, 2014               [Page 52]
     2962Fielding & Reschke      Expires November 10, 2014              [Page 52]
    29632963
    29642964
     
    30173017
    30183018
    3019 Fielding & Reschke      Expires November 9, 2014               [Page 53]
     3019Fielding & Reschke      Expires November 10, 2014              [Page 53]
    30203020
    30213021
     
    30743074
    30753075
    3076 Fielding & Reschke      Expires November 9, 2014               [Page 54]
     3076Fielding & Reschke      Expires November 10, 2014              [Page 54]
    30773077
    30783078
     
    31313131
    31323132
    3133 Fielding & Reschke      Expires November 9, 2014               [Page 55]
     3133Fielding & Reschke      Expires November 10, 2014              [Page 55]
    31343134
    31353135
     
    31883188
    31893189
    3190 Fielding & Reschke      Expires November 9, 2014               [Page 56]
     3190Fielding & Reschke      Expires November 10, 2014              [Page 56]
    31913191
    31923192
     
    32453245
    32463246
    3247 Fielding & Reschke      Expires November 9, 2014               [Page 57]
     3247Fielding & Reschke      Expires November 10, 2014              [Page 57]
    32483248
    32493249
     
    33023302
    33033303
    3304 Fielding & Reschke      Expires November 9, 2014               [Page 58]
     3304Fielding & Reschke      Expires November 10, 2014              [Page 58]
    33053305
    33063306
     
    33593359
    33603360
    3361 Fielding & Reschke      Expires November 9, 2014               [Page 59]
     3361Fielding & Reschke      Expires November 10, 2014              [Page 59]
    33623362
    33633363
     
    34163416
    34173417
    3418 Fielding & Reschke      Expires November 9, 2014               [Page 60]
     3418Fielding & Reschke      Expires November 10, 2014              [Page 60]
    34193419
    34203420
     
    34733473
    34743474
    3475 Fielding & Reschke      Expires November 9, 2014               [Page 61]
     3475Fielding & Reschke      Expires November 10, 2014              [Page 61]
    34763476
    34773477
     
    35303530
    35313531
    3532 Fielding & Reschke      Expires November 9, 2014               [Page 62]
     3532Fielding & Reschke      Expires November 10, 2014              [Page 62]
    35333533
    35343534
     
    35873587
    35883588
    3589 Fielding & Reschke      Expires November 9, 2014               [Page 63]
     3589Fielding & Reschke      Expires November 10, 2014              [Page 63]
    35903590
    35913591
     
    36443644
    36453645
    3646 Fielding & Reschke      Expires November 9, 2014               [Page 64]
     3646Fielding & Reschke      Expires November 10, 2014              [Page 64]
    36473647
    36483648
     
    37013701
    37023702
    3703 Fielding & Reschke      Expires November 9, 2014               [Page 65]
     3703Fielding & Reschke      Expires November 10, 2014              [Page 65]
    37043704
    37053705
     
    37583758
    37593759
    3760 Fielding & Reschke      Expires November 9, 2014               [Page 66]
     3760Fielding & Reschke      Expires November 10, 2014              [Page 66]
    37613761
    37623762
     
    38153815
    38163816
    3817 Fielding & Reschke      Expires November 9, 2014               [Page 67]
     3817Fielding & Reschke      Expires November 10, 2014              [Page 67]
    38183818
    38193819
     
    38723872
    38733873
    3874 Fielding & Reschke      Expires November 9, 2014               [Page 68]
     3874Fielding & Reschke      Expires November 10, 2014              [Page 68]
    38753875
    38763876
     
    39293929
    39303930
    3931 Fielding & Reschke      Expires November 9, 2014               [Page 69]
     3931Fielding & Reschke      Expires November 10, 2014              [Page 69]
    39323932
    39333933
     
    39863986
    39873987
    3988 Fielding & Reschke      Expires November 9, 2014               [Page 70]
     3988Fielding & Reschke      Expires November 10, 2014              [Page 70]
    39893989
    39903990
     
    40434043
    40444044
    4045 Fielding & Reschke      Expires November 9, 2014               [Page 71]
     4045Fielding & Reschke      Expires November 10, 2014              [Page 71]
    40464046
    40474047
     
    41004100
    41014101
    4102 Fielding & Reschke      Expires November 9, 2014               [Page 72]
     4102Fielding & Reschke      Expires November 10, 2014              [Page 72]
    41034103
    41044104
     
    41574157
    41584158
    4159 Fielding & Reschke      Expires November 9, 2014               [Page 73]
     4159Fielding & Reschke      Expires November 10, 2014              [Page 73]
    41604160
    41614161
     
    42144214
    42154215
    4216 Fielding & Reschke      Expires November 9, 2014               [Page 74]
     4216Fielding & Reschke      Expires November 10, 2014              [Page 74]
    42174217
    42184218
     
    42714271
    42724272
    4273 Fielding & Reschke      Expires November 9, 2014               [Page 75]
     4273Fielding & Reschke      Expires November 10, 2014              [Page 75]
    42744274
    42754275
     
    43284328
    43294329
    4330 Fielding & Reschke      Expires November 9, 2014               [Page 76]
     4330Fielding & Reschke      Expires November 10, 2014              [Page 76]
    43314331
    43324332
     
    43854385
    43864386
    4387 Fielding & Reschke      Expires November 9, 2014               [Page 77]
     4387Fielding & Reschke      Expires November 10, 2014              [Page 77]
    43884388
    43894389
     
    44424442
    44434443
    4444 Fielding & Reschke      Expires November 9, 2014               [Page 78]
     4444Fielding & Reschke      Expires November 10, 2014              [Page 78]
    44454445
    44464446
     
    44994499
    45004500
    4501 Fielding & Reschke      Expires November 9, 2014               [Page 79]
     4501Fielding & Reschke      Expires November 10, 2014              [Page 79]
    45024502
    45034503
     
    45564556
    45574557
    4558 Fielding & Reschke      Expires November 9, 2014               [Page 80]
     4558Fielding & Reschke      Expires November 10, 2014              [Page 80]
    45594559
    45604560
     
    456445648.4.1.  Procedure
    45654565
    4566    Content Coding registrations MUST include the following fields:
     4566   Content coding registrations MUST include the following fields:
    45674567
    45684568   o  Name
     
    45784578
    45794579   Values to be added to this namespace require IETF Review (see Section
    4580    4.1 of [RFC5226]), and MUST conform to the purpose of content coding
     4580   4.1 of [RFC5226]) and MUST conform to the purpose of content coding
    45814581   defined in this section.
    45824582
     
    46134613
    46144614
    4615 Fielding & Reschke      Expires November 9, 2014               [Page 81]
     4615Fielding & Reschke      Expires November 10, 2014              [Page 81]
    46164616
    46174617
     
    46704670
    46714671
    4672 Fielding & Reschke      Expires November 9, 2014               [Page 82]
     4672Fielding & Reschke      Expires November 10, 2014              [Page 82]
    46734673
    46744674
     
    47274727
    47284728
    4729 Fielding & Reschke      Expires November 9, 2014               [Page 83]
     4729Fielding & Reschke      Expires November 10, 2014              [Page 83]
    47304730
    47314731
     
    47844784
    47854785
    4786 Fielding & Reschke      Expires November 9, 2014               [Page 84]
     4786Fielding & Reschke      Expires November 10, 2014              [Page 84]
    47874787
    47884788
     
    48414841
    48424842
    4843 Fielding & Reschke      Expires November 9, 2014               [Page 85]
     4843Fielding & Reschke      Expires November 10, 2014              [Page 85]
    48444844
    48454845
     
    48984898
    48994899
    4900 Fielding & Reschke      Expires November 9, 2014               [Page 86]
     4900Fielding & Reschke      Expires November 10, 2014              [Page 86]
    49014901
    49024902
     
    49554955
    49564956
    4957 Fielding & Reschke      Expires November 9, 2014               [Page 87]
     4957Fielding & Reschke      Expires November 10, 2014              [Page 87]
    49584958
    49594959
     
    50125012
    50135013
    5014 Fielding & Reschke      Expires November 9, 2014               [Page 88]
     5014Fielding & Reschke      Expires November 10, 2014              [Page 88]
    50155015
    50165016
     
    50695069
    50705070
    5071 Fielding & Reschke      Expires November 9, 2014               [Page 89]
     5071Fielding & Reschke      Expires November 10, 2014              [Page 89]
    50725072
    50735073
     
    51265126
    51275127
    5128 Fielding & Reschke      Expires November 9, 2014               [Page 90]
     5128Fielding & Reschke      Expires November 10, 2014              [Page 90]
    51295129
    51305130
     
    51835183
    51845184
    5185 Fielding & Reschke      Expires November 9, 2014               [Page 91]
     5185Fielding & Reschke      Expires November 10, 2014              [Page 91]
    51865186
    51875187
     
    52055205   to rewrite the method from POST to GET.  (Sections 6.4.2 and 6.4.3)
    52065206
    5207    The description of 303 (See Other) status code has been changed to
    5208    allow it to be cached if explicit freshness information is given, and
    5209    a specific definition has been added for a 303 response to GET.
     5207   The description of the 303 (See Other) status code has been changed
     5208   to allow it to be cached if explicit freshness information is given,
     5209   and a specific definition has been added for a 303 response to GET.
    52105210   (Section 6.4.4)
    52115211
     
    52405240
    52415241
    5242 Fielding & Reschke      Expires November 9, 2014               [Page 92]
     5242Fielding & Reschke      Expires November 10, 2014              [Page 92]
    52435243
    52445244
     
    52485248   (Section 8.2)
    52495249
    5250    Registration of Content Codings has been changed to require IETF
     5250   Registration of content codings has been changed to require IETF
    52515251   Review.  (Section 8.4)
    52525252
     
    52975297
    52985298
    5299 Fielding & Reschke      Expires November 9, 2014               [Page 93]
     5299Fielding & Reschke      Expires November 10, 2014              [Page 93]
    53005300
    53015301
     
    53545354
    53555355
    5356 Fielding & Reschke      Expires November 9, 2014               [Page 94]
     5356Fielding & Reschke      Expires November 10, 2014              [Page 94]
    53575357
    53585358
     
    54115411
    54125412
    5413 Fielding & Reschke      Expires November 9, 2014               [Page 95]
     5413Fielding & Reschke      Expires November 10, 2014              [Page 95]
    54145414
    54155415
     
    54685468
    54695469
    5470 Fielding & Reschke      Expires November 9, 2014               [Page 96]
     5470Fielding & Reschke      Expires November 10, 2014              [Page 96]
    54715471
    54725472
     
    55255525
    55265526
    5527 Fielding & Reschke      Expires November 9, 2014               [Page 97]
     5527Fielding & Reschke      Expires November 10, 2014              [Page 97]
    55285528
    55295529
     
    55825582
    55835583
    5584 Fielding & Reschke      Expires November 9, 2014               [Page 98]
     5584Fielding & Reschke      Expires November 10, 2014              [Page 98]
    55855585
    55865586
     
    56395639
    56405640
    5641 Fielding & Reschke      Expires November 9, 2014               [Page 99]
     5641Fielding & Reschke      Expires November 10, 2014              [Page 99]
    56425642
    56435643
     
    56965696
    56975697
    5698 Fielding & Reschke      Expires November 9, 2014              [Page 100]
     5698Fielding & Reschke      Expires November 10, 2014             [Page 100]
    56995699
    57005700
     
    57535753
    57545754
    5755 Fielding & Reschke      Expires November 9, 2014              [Page 101]
    5756 
    5757 
     5755Fielding & Reschke      Expires November 10, 2014             [Page 101]
     5756
     5757
  • draft-ietf-httpbis/latest/auth48/rfc7230.abdiff.txt

    r2661 r2663  
    77 Obsoletes: 2145, 2616                                    J. Reschke, Ed.
    88 (if approved)                                                 greenbytes
    9  Updates: 2817, 2818 (if approved)                            May 8, 2014
     9 Updates: 2817, 2818 (if approved)                            May 9, 2014
    1010 Intended status: Standards Track
    11  Expires: November 9, 2014
     11 Expires: November 10, 2014
    1212
    1313NEW:
     
    9292OLD:
    9393
    94     This Internet-Draft will expire on November 9, 2014.
     94    This Internet-Draft will expire on November 10, 2014.
    9595
    9696NEW:
  • draft-ietf-httpbis/latest/auth48/rfc7230.diff.html

    r2661 r2663  
    4444      <tr><td><a name="diff0002" /></td></tr>
    4545      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">(if approved)                                                 greenbytes</span></td><td> </td><td class="rblock">Updates: 2817, 2818                                           <span class="insert">greenbytes</span></td><td class="lineno" valign="top"></td></tr>
    46       <tr><td class="lineno" valign="top"></td><td class="lblock">Updates: 2817, 2818 <span class="delete">(if approved)                            May 8, 2014</span></td><td> </td><td class="rblock"><span class="insert">Category:</span> Standards Track                                       <span class="insert">May</span> 2014</td><td class="lineno" valign="top"></td></tr>
     46      <tr><td class="lineno" valign="top"></td><td class="lblock">Updates: 2817, 2818 <span class="delete">(if approved)                            May 9, 2014</span></td><td> </td><td class="rblock"><span class="insert">Category:</span> Standards Track                                       <span class="insert">May</span> 2014</td><td class="lineno" valign="top"></td></tr>
    4747      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">Intended status:</span> Standards Track</td><td> </td><td class="rblock"><span class="insert">ISSN: 2070-1721</span></td><td class="lineno" valign="top"></td></tr>
    48       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">Expires: November 9,</span> 2014</td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     48      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">Expires: November 10,</span> 2014</td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    4949      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    5050      <tr><td class="lineno" valign="top"></td><td class="left">   Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing</td><td> </td><td class="right">   Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing</td><td class="lineno" valign="top"></td></tr>
     
    9696      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    9797      <tr><td><a name="diff0007" /></td></tr>
    98       <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">This Internet-Draft will expire</span> on <span class="delete">November 9, 2014.</span></td><td> </td><td class="rblock">   <span class="insert">Information about the current status of this document, any errata,</span></td><td class="lineno" valign="top"></td></tr>
     98      <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">This Internet-Draft will expire</span> on <span class="delete">November 10, 2014.</span></td><td> </td><td class="rblock">   <span class="insert">Information about the current status of this document, any errata,</span></td><td class="lineno" valign="top"></td></tr>
    9999      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   and how to provide feedback</span> on <span class="insert">it may be obtained at</span></td><td class="lineno" valign="top"></td></tr>
    100100      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   http://www.rfc-editor.org/info/rfc7230.</span></td><td class="lineno" valign="top"></td></tr>
  • draft-ietf-httpbis/latest/auth48/rfc7231.abdiff.txt

    r2660 r2663  
    77 Obsoletes: 2616 (if approved)                            J. Reschke, Ed.
    88 Updates: 2817 (if approved)                                   greenbytes
    9  Intended status: Standards Track                             May 8, 2014
    10  Expires: November 9, 2014
     9 Intended status: Standards Track                             May 9, 2014
     10 Expires: November 10, 2014
    1111
    1212NEW:
     
    9191OLD:
    9292
    93     This Internet-Draft will expire on November 9, 2014.
     93    This Internet-Draft will expire on November 10, 2014.
    9494
    9595NEW:
     
    387387
    388388
    389 Section 2., paragraph 1:
    390 OLD:
    391 
    392     The target of an HTTP request is called a resource.  HTTP does not
    393     limit the nature of a resource; it merely defines an interface that
    394     might be used to interact with resources.  Each resource is
    395     identified by a Uniform Resource Identifier (URI), as described in
    396     Section 2.7 of [RFC7230].
    397 
    398 NEW:
    399 
    400     The target of an HTTP request is called a "resource".  HTTP does not
    401     limit the nature of a resource; it merely defines an interface that
    402     might be used to interact with resources.  Each resource is
    403     identified by a Uniform Resource Identifier (URI), as described in
    404     Section 2.7 of [RFC7230].
    405 
    406 
    407 Section 3.1.1.1., paragraph 1:
    408 OLD:
    409 
    410     HTTP uses Internet Media Types [RFC2046] in the Content-Type
    411     (Section 3.1.1.5) and Accept (Section 5.3.2) header fields in order
    412     to provide open and extensible data typing and type negotiation.
    413     Media types define both a data format and various processing models:
    414     how to process that data in accordance with each context in which it
    415     is received.
    416 
    417 NEW:
    418 
    419     HTTP uses Internet media types [RFC2046] in the Content-Type
    420     (Section 3.1.1.5) and Accept (Section 5.3.2) header fields in order
    421     to provide open and extensible data typing and type negotiation.
    422     Media types define both a data format and various processing models:
    423     how to process that data in accordance with each context in which it
    424     is received.
    425 
    426 
    427389Section 3.1.1.1., paragraph 5:
    428390OLD:
     
    446408OLD:
    447409
    448     Charset names ought to be registered in the IANA Character Set
     410    Charset names ought to be registered in the IANA "Character Sets"
    449411    registry (<http://www.iana.org/assignments/character-sets>) according
    450412    to the procedures defined in [RFC2978].
     
    680642    If the target URI was obtained from a source that does not have its
    681643    own URI (e.g., input from the user keyboard, or an entry within the
    682     user's bookmarks/favorites), the user agent MUST either exclude
    683     Referer or send it with a value of "about:blank".
     644    user's bookmarks/favorites), the user agent MUST either exclude the
     645    Referer field or send it with a value of "about:blank".
    684646
    685647NEW:
     
    10751037
    10761038
    1077 Section 8.4.1., paragraph 1:
    1078 OLD:
    1079 
    1080     Content Coding registrations MUST include the following fields:
    1081 
    1082 NEW:
    1083 
    1084     Content coding registrations MUST include the following fields:
    1085 
    1086 
    1087 Section 8.4.1., paragraph 6:
    1088 OLD:
    1089 
    1090     Values to be added to this namespace require IETF Review (see Section
    1091     4.1 of [RFC5226]), and MUST conform to the purpose of content coding
    1092     defined in this section.
    1093 
    1094 NEW:
    1095 
    1096     Values to be added to this namespace require IETF Review (see Section
    1097     4.1 of [RFC5226]) and MUST conform to the purpose of content coding
    1098     defined in this section.
    1099 
    1100 
    11011039Section 8.4.2., paragraph 1:
    11021040OLD:
     
    15081446OLD:
    15091447
    1510     The description of 303 (See Other) status code has been changed to
    1511     allow it to be cached if explicit freshness information is given, and
    1512     a specific definition has been added for a 303 response to GET.
     1448    The description of the 303 (See Other) status code has been changed
     1449    to allow it to be cached if explicit freshness information is given,
     1450    and a specific definition has been added for a 303 response to GET.
    15131451    (Section 6.4.4)
    15141452
     
    16301568OLD:
    16311569
    1632     Registration of Content Codings has been changed to require IETF
     1570    Registration of content codings has been changed to require IETF
    16331571    Review.  (Section 8.4)
    16341572
  • draft-ietf-httpbis/latest/auth48/rfc7231.diff.html

    r2660 r2663  
    4343      <tr><td class="lineno" valign="top"></td><td class="lblock">Obsoletes: 2616 <span class="delete">(if approved)</span>                            J. Reschke, Ed.</td><td> </td><td class="rblock">Obsoletes: 2616                                          J. Reschke, Ed.</td><td class="lineno" valign="top"></td></tr>
    4444      <tr><td class="lineno" valign="top"></td><td class="lblock">Updates: 2817 <span class="delete">(if approved)</span>                                   greenbytes</td><td> </td><td class="rblock">Updates: 2817                                                 greenbytes</td><td class="lineno" valign="top"></td></tr>
    45       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">Intended status:</span> Standards Track                             May <span class="delete">8, 2014</span></td><td> </td><td class="rblock"><span class="insert">Category:</span> Standards Track                                       May 2014</td><td class="lineno" valign="top"></td></tr>
    46       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">Expires: November 9,</span> 2014</td><td> </td><td class="rblock"><span class="insert">ISSN: 2070-1721</span></td><td class="lineno" valign="top"></td></tr>
     45      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">Intended status:</span> Standards Track                             May <span class="delete">9, 2014</span></td><td> </td><td class="rblock"><span class="insert">Category:</span> Standards Track                                       May 2014</td><td class="lineno" valign="top"></td></tr>
     46      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">Expires: November 10,</span> 2014</td><td> </td><td class="rblock"><span class="insert">ISSN: 2070-1721</span></td><td class="lineno" valign="top"></td></tr>
    4747      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    4848      <tr><td class="lineno" valign="top"></td><td class="left">     Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content</td><td> </td><td class="right">     Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content</td><td class="lineno" valign="top"></td></tr>
     
    9494      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    9595      <tr><td><a name="diff0006" /></td></tr>
    96       <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">This Internet-Draft will expire</span> on <span class="delete">November 9, 2014.</span></td><td> </td><td class="rblock">   <span class="insert">Information about the current status of this document, any errata,</span></td><td class="lineno" valign="top"></td></tr>
     96      <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">This Internet-Draft will expire</span> on <span class="delete">November 10, 2014.</span></td><td> </td><td class="rblock">   <span class="insert">Information about the current status of this document, any errata,</span></td><td class="lineno" valign="top"></td></tr>
    9797      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   and how to provide feedback</span> on <span class="insert">it may be obtained at</span></td><td class="lineno" valign="top"></td></tr>
    9898      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   http://www.rfc-editor.org/info/rfc7231.</span></td><td class="lineno" valign="top"></td></tr>
     
    138138      <tr><td class="lineno" valign="top"></td><td class="left">   parses each message received, interprets the message semantics in</td><td> </td><td class="right">   parses each message received, interprets the message semantics in</td><td class="lineno" valign="top"></td></tr>
    139139      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    140       <tr bgcolor="gray" ><td></td><th><a name="part-l3" /><small>skipping to change at</small><em> page 7, line 11</em></th><th> </th><th><a name="part-r3" /><small>skipping to change at</small><em> page 7, line 11</em></th><td></td></tr>
    141       <tr><td class="lineno" valign="top"></td><td class="left">   repetition).  Appendix C describes rules imported from other</td><td> </td><td class="right">   repetition).  Appendix C describes rules imported from other</td><td class="lineno" valign="top"></td></tr>
    142       <tr><td class="lineno" valign="top"></td><td class="left">   documents.  Appendix D shows the collected grammar with all list</td><td> </td><td class="right">   documents.  Appendix D shows the collected grammar with all list</td><td class="lineno" valign="top"></td></tr>
    143       <tr><td class="lineno" valign="top"></td><td class="left">   operators expanded to standard ABNF notation.</td><td> </td><td class="right">   operators expanded to standard ABNF notation.</td><td class="lineno" valign="top"></td></tr>
    144       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    145       <tr><td class="lineno" valign="top"></td><td class="left">   This specification uses the terms "character", "character encoding</td><td> </td><td class="right">   This specification uses the terms "character", "character encoding</td><td class="lineno" valign="top"></td></tr>
    146       <tr><td class="lineno" valign="top"></td><td class="left">   scheme", "charset", and "protocol element" as they are defined in</td><td> </td><td class="right">   scheme", "charset", and "protocol element" as they are defined in</td><td class="lineno" valign="top"></td></tr>
    147       <tr><td class="lineno" valign="top"></td><td class="left">   [RFC6365].</td><td> </td><td class="right">   [RFC6365].</td><td class="lineno" valign="top"></td></tr>
    148       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    149       <tr><td class="lineno" valign="top"></td><td class="left">2.  Resources</td><td> </td><td class="right">2.  Resources</td><td class="lineno" valign="top"></td></tr>
    150       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    151       <tr><td><a name="diff0009" /></td></tr>
    152       <tr><td class="lineno" valign="top"></td><td class="lblock">   The target of an HTTP request is called a <span class="delete">resource</span>.  HTTP does not</td><td> </td><td class="rblock">   The target of an HTTP request is called a <span class="insert">"resource"</span>.  HTTP does not</td><td class="lineno" valign="top"></td></tr>
    153       <tr><td class="lineno" valign="top"></td><td class="left">   limit the nature of a resource; it merely defines an interface that</td><td> </td><td class="right">   limit the nature of a resource; it merely defines an interface that</td><td class="lineno" valign="top"></td></tr>
    154       <tr><td class="lineno" valign="top"></td><td class="left">   might be used to interact with resources.  Each resource is</td><td> </td><td class="right">   might be used to interact with resources.  Each resource is</td><td class="lineno" valign="top"></td></tr>
    155       <tr><td class="lineno" valign="top"></td><td class="left">   identified by a Uniform Resource Identifier (URI), as described in</td><td> </td><td class="right">   identified by a Uniform Resource Identifier (URI), as described in</td><td class="lineno" valign="top"></td></tr>
    156       <tr><td class="lineno" valign="top"></td><td class="left">   Section 2.7 of [RFC7230].</td><td> </td><td class="right">   Section 2.7 of [RFC7230].</td><td class="lineno" valign="top"></td></tr>
    157       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    158       <tr><td class="lineno" valign="top"></td><td class="left">   When a client constructs an HTTP/1.1 request message, it sends the</td><td> </td><td class="right">   When a client constructs an HTTP/1.1 request message, it sends the</td><td class="lineno" valign="top"></td></tr>
    159       <tr><td class="lineno" valign="top"></td><td class="left">   target URI in one of various forms, as defined in (Section 5.3 of</td><td> </td><td class="right">   target URI in one of various forms, as defined in (Section 5.3 of</td><td class="lineno" valign="top"></td></tr>
    160       <tr><td class="lineno" valign="top"></td><td class="left">   [RFC7230]).  When a request is received, the server reconstructs an</td><td> </td><td class="right">   [RFC7230]).  When a request is received, the server reconstructs an</td><td class="lineno" valign="top"></td></tr>
    161       <tr><td class="lineno" valign="top"></td><td class="left">   effective request URI for the target resource (Section 5.5 of</td><td> </td><td class="right">   effective request URI for the target resource (Section 5.5 of</td><td class="lineno" valign="top"></td></tr>
    162       <tr><td class="lineno" valign="top"></td><td class="left">   [RFC7230]).</td><td> </td><td class="right">   [RFC7230]).</td><td class="lineno" valign="top"></td></tr>
    163       <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    164       <tr bgcolor="gray" ><td></td><th><a name="part-l4" /><small>skipping to change at</small><em> page 8, line 32</em></th><th> </th><th><a name="part-r4" /><small>skipping to change at</small><em> page 8, line 32</em></th><td></td></tr>
    165       <tr><td class="lineno" valign="top"></td><td class="left">   | Content-Type      | Section 3.1.1.5 |</td><td> </td><td class="right">   | Content-Type      | Section 3.1.1.5 |</td><td class="lineno" valign="top"></td></tr>
    166       <tr><td class="lineno" valign="top"></td><td class="left">   | Content-Encoding  | Section 3.1.2.2 |</td><td> </td><td class="right">   | Content-Encoding  | Section 3.1.2.2 |</td><td class="lineno" valign="top"></td></tr>
    167       <tr><td class="lineno" valign="top"></td><td class="left">   | Content-Language  | Section 3.1.3.2 |</td><td> </td><td class="right">   | Content-Language  | Section 3.1.3.2 |</td><td class="lineno" valign="top"></td></tr>
    168       <tr><td class="lineno" valign="top"></td><td class="left">   | Content-Location  | Section 3.1.4.2 |</td><td> </td><td class="right">   | Content-Location  | Section 3.1.4.2 |</td><td class="lineno" valign="top"></td></tr>
    169       <tr><td class="lineno" valign="top"></td><td class="left">   +-------------------+-----------------+</td><td> </td><td class="right">   +-------------------+-----------------+</td><td class="lineno" valign="top"></td></tr>
    170       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    171       <tr><td class="lineno" valign="top"></td><td class="left">3.1.1.  Processing Representation Data</td><td> </td><td class="right">3.1.1.  Processing Representation Data</td><td class="lineno" valign="top"></td></tr>
    172       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    173       <tr><td class="lineno" valign="top"></td><td class="left">3.1.1.1.  Media Type</td><td> </td><td class="right">3.1.1.1.  Media Type</td><td class="lineno" valign="top"></td></tr>
    174       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    175       <tr><td><a name="diff0010" /></td></tr>
    176       <tr><td class="lineno" valign="top"></td><td class="lblock">   HTTP uses Internet <span class="delete">Media T</span>ypes [RFC2046] in the Content-Type</td><td> </td><td class="rblock">   HTTP uses Internet <span class="insert">media t</span>ypes [RFC2046] in the Content-Type</td><td class="lineno" valign="top"></td></tr>
    177       <tr><td class="lineno" valign="top"></td><td class="left">   (Section 3.1.1.5) and Accept (Section 5.3.2) header fields in order</td><td> </td><td class="right">   (Section 3.1.1.5) and Accept (Section 5.3.2) header fields in order</td><td class="lineno" valign="top"></td></tr>
    178       <tr><td class="lineno" valign="top"></td><td class="left">   to provide open and extensible data typing and type negotiation.</td><td> </td><td class="right">   to provide open and extensible data typing and type negotiation.</td><td class="lineno" valign="top"></td></tr>
    179       <tr><td class="lineno" valign="top"></td><td class="left">   Media types define both a data format and various processing models:</td><td> </td><td class="right">   Media types define both a data format and various processing models:</td><td class="lineno" valign="top"></td></tr>
    180       <tr><td class="lineno" valign="top"></td><td class="left">   how to process that data in accordance with each context in which it</td><td> </td><td class="right">   how to process that data in accordance with each context in which it</td><td class="lineno" valign="top"></td></tr>
    181       <tr><td class="lineno" valign="top"></td><td class="left">   is received.</td><td> </td><td class="right">   is received.</td><td class="lineno" valign="top"></td></tr>
     140      <tr bgcolor="gray" ><td></td><th><a name="part-l3" /><small>skipping to change at</small><em> page 8, line 48</em></th><th> </th><th><a name="part-r3" /><small>skipping to change at</small><em> page 8, line 48</em></th><td></td></tr>
    182141      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    183142      <tr><td class="lineno" valign="top"></td><td class="left">     media-type = type "/" subtype *( OWS ";" OWS parameter )</td><td> </td><td class="right">     media-type = type "/" subtype *( OWS ";" OWS parameter )</td><td class="lineno" valign="top"></td></tr>
     
    190149      <tr><td class="lineno" valign="top"></td><td class="left">     parameter      = token "=" ( token / quoted-string )</td><td> </td><td class="right">     parameter      = token "=" ( token / quoted-string )</td><td class="lineno" valign="top"></td></tr>
    191150      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    192       <tr><td><a name="diff0011" /></td></tr>
     151      <tr><td><a name="diff0009" /></td></tr>
    193152      <tr><td class="lineno" valign="top"></td><td class="lblock">   The type, subtype, and parameter name tokens are <span class="delete">case-insensitive.</span></td><td> </td><td class="rblock">   The type, subtype, and parameter name tokens are <span class="insert">case insensitive.</span></td><td class="lineno" valign="top"></td></tr>
    194153      <tr><td class="lineno" valign="top"></td><td class="lblock">   Parameter values might or might not be <span class="delete">case-sensitive,</span> depending on</td><td> </td><td class="rblock">   Parameter values might or might not be <span class="insert">case sensitive,</span> depending on</td><td class="lineno" valign="top"></td></tr>
     
    204163      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    205164      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    206       <tr bgcolor="gray" ><td></td><th><a name="part-l5" /><small>skipping to change at</small><em> page 9, line 32</em></th><th> </th><th><a name="part-r5" /><small>skipping to change at</small><em> page 9, line 32</em></th><td></td></tr>
    207       <tr><td class="lineno" valign="top"></td><td class="left">      around the "=" character.</td><td> </td><td class="right">      around the "=" character.</td><td class="lineno" valign="top"></td></tr>
     165      <tr bgcolor="gray" ><td></td><th><a name="part-l4" /><small>skipping to change at</small><em> page 9, line 33</em></th><th> </th><th><a name="part-r4" /><small>skipping to change at</small><em> page 9, line 33</em></th><td></td></tr>
    208166      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    209167      <tr><td class="lineno" valign="top"></td><td class="left">3.1.1.2.  Charset</td><td> </td><td class="right">3.1.1.2.  Charset</td><td class="lineno" valign="top"></td></tr>
     
    215173      <tr><td class="lineno" valign="top"></td><td class="left">     charset = token</td><td> </td><td class="right">     charset = token</td><td class="lineno" valign="top"></td></tr>
    216174      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    217       <tr><td><a name="diff0012" /></td></tr>
    218       <tr><td class="lineno" valign="top"></td><td class="lblock">   Charset names ought to be registered in the IANA <span class="delete">Character Set</span></td><td> </td><td class="rblock">   Charset names ought to be registered in the IANA <span class="insert">"Character Sets"</span></td><td class="lineno" valign="top"></td></tr>
     175      <tr><td class="lineno" valign="top"></td><td class="left">   Charset names ought to be registered in the IANA "Character Sets"</td><td> </td><td class="right">   Charset names ought to be registered in the IANA "Character Sets"</td><td class="lineno" valign="top"></td></tr>
     176      <tr><td><a name="diff0010" /></td></tr>
    219177      <tr><td class="lineno" valign="top"></td><td class="lblock">   registry <span class="delete">(&lt;http://www.iana.org/assignments/character-sets&gt;)</span> according</td><td> </td><td class="rblock">   registry <span class="insert">&lt;http://www.iana.org/assignments/character-sets&gt;</span> according</td><td class="lineno" valign="top"></td></tr>
    220178      <tr><td class="lineno" valign="top"></td><td class="left">   to the procedures defined in [RFC2978].</td><td> </td><td class="right">   to the procedures defined in [RFC2978].</td><td class="lineno" valign="top"></td></tr>
     
    235193      <tr><td class="lineno" valign="top"></td><td class="left">   MIME's canonical form requires that media subtypes of the "text" type</td><td> </td><td class="right">   MIME's canonical form requires that media subtypes of the "text" type</td><td class="lineno" valign="top"></td></tr>
    236194      <tr><td class="lineno" valign="top"></td><td class="left">   use CRLF as the text line break.  HTTP allows the transfer of text</td><td> </td><td class="right">   use CRLF as the text line break.  HTTP allows the transfer of text</td><td class="lineno" valign="top"></td></tr>
    237       <tr><td><a name="diff0013" /></td></tr>
     195      <tr><td><a name="diff0011" /></td></tr>
    238196      <tr><td class="lineno" valign="top"></td><td class="lblock">   media with plain <span class="delete">CR</span> or <span class="delete">LF</span> alone representing a line break, when such</td><td> </td><td class="rblock">   media with plain <span class="insert">carriage return (CR)</span> or <span class="insert">line feed (LF)</span> alone</td><td class="lineno" valign="top"></td></tr>
    239197      <tr><td class="lineno" valign="top"></td><td class="lblock">   line breaks are consistent for an entire representation.  An HTTP</td><td> </td><td class="rblock">   representing a line break, when such line breaks are consistent for</td><td class="lineno" valign="top"></td></tr>
     
    257215      <tr><td class="lineno" valign="top"></td><td class="left">   [RFC2046], and include a boundary parameter as part of the media type</td><td> </td><td class="right">   [RFC2046], and include a boundary parameter as part of the media type</td><td class="lineno" valign="top"></td></tr>
    258216      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    259       <tr bgcolor="gray" ><td></td><th><a name="part-l6" /><small>skipping to change at</small><em> page 11, line 35</em></th><th> </th><th><a name="part-r6" /><small>skipping to change at</small><em> page 11, line 35</em></th><td></td></tr>
     217      <tr bgcolor="gray" ><td></td><th><a name="part-l5" /><small>skipping to change at</small><em> page 11, line 35</em></th><th> </th><th><a name="part-r5" /><small>skipping to change at</small><em> page 11, line 35</em></th><td></td></tr>
    260218      <tr><td class="lineno" valign="top"></td><td class="left">   Content coding values indicate an encoding transformation that has</td><td> </td><td class="right">   Content coding values indicate an encoding transformation that has</td><td class="lineno" valign="top"></td></tr>
    261219      <tr><td class="lineno" valign="top"></td><td class="left">   been or can be applied to a representation.  Content codings are</td><td> </td><td class="right">   been or can be applied to a representation.  Content codings are</td><td class="lineno" valign="top"></td></tr>
     
    268226      <tr><td class="lineno" valign="top"></td><td class="left">     content-coding   = token</td><td> </td><td class="right">     content-coding   = token</td><td class="lineno" valign="top"></td></tr>
    269227      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    270       <tr><td><a name="diff0014" /></td></tr>
     228      <tr><td><a name="diff0012" /></td></tr>
    271229      <tr><td class="lineno" valign="top"></td><td class="lblock">   All content-coding values are case<span class="delete">-</span>insensitive and ought to be</td><td> </td><td class="rblock">   All content-coding values are case<span class="insert"> </span>insensitive and ought to be</td><td class="lineno" valign="top"></td></tr>
    272230      <tr><td class="lineno" valign="top"></td><td class="left">   registered within the "HTTP Content Coding Registry", as defined in</td><td> </td><td class="right">   registered within the "HTTP Content Coding Registry", as defined in</td><td class="lineno" valign="top"></td></tr>
     
    281239      <tr><td class="lineno" valign="top"></td><td class="left">      deflate: See Section 4.2.2 of [RFC7230].</td><td> </td><td class="right">      deflate: See Section 4.2.2 of [RFC7230].</td><td class="lineno" valign="top"></td></tr>
    282240      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    283       <tr bgcolor="gray" ><td></td><th><a name="part-l7" /><small>skipping to change at</small><em> page 14, line 5</em></th><th> </th><th><a name="part-r7" /><small>skipping to change at</small><em> page 14, line 5</em></th><td></td></tr>
     241      <tr bgcolor="gray" ><td></td><th><a name="part-l6" /><small>skipping to change at</small><em> page 14, line 5</em></th><th> </th><th><a name="part-r6" /><small>skipping to change at</small><em> page 14, line 5</em></th><td></td></tr>
    284242      <tr><td class="lineno" valign="top"></td><td class="left">   Content-Language is to allow a user to identify and differentiate</td><td> </td><td class="right">   Content-Language is to allow a user to identify and differentiate</td><td class="lineno" valign="top"></td></tr>
    285243      <tr><td class="lineno" valign="top"></td><td class="left">   representations according to the users' own preferred language.</td><td> </td><td class="right">   representations according to the users' own preferred language.</td><td class="lineno" valign="top"></td></tr>
     
    292250      <tr><td class="lineno" valign="top"></td><td class="left">   is intended for all language audiences.  This might mean that the</td><td> </td><td class="right">   is intended for all language audiences.  This might mean that the</td><td class="lineno" valign="top"></td></tr>
    293251      <tr><td class="lineno" valign="top"></td><td class="left">   sender does not consider it to be specific to any natural language,</td><td> </td><td class="right">   sender does not consider it to be specific to any natural language,</td><td class="lineno" valign="top"></td></tr>
    294       <tr><td><a name="diff0015" /></td></tr>
     252      <tr><td><a name="diff0013" /></td></tr>
    295253      <tr><td class="lineno" valign="top"></td><td class="lblock">   or that the sender does not know <span class="delete">for which language it is intend</span>ed.</td><td> </td><td class="rblock">   or that the sender does not know <span class="insert">which language is being us</span>ed.</td><td class="lineno" valign="top"></td></tr>
    296254      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     
    305263      <tr><td class="lineno" valign="top"></td><td class="left">   representation does not mean that it is intended for multiple</td><td> </td><td class="right">   representation does not mean that it is intended for multiple</td><td class="lineno" valign="top"></td></tr>
    306264      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    307       <tr bgcolor="gray" ><td></td><th><a name="part-l8" /><small>skipping to change at</small><em> page 19, line 21</em></th><th> </th><th><a name="part-r8" /><small>skipping to change at</small><em> page 19, line 21</em></th><td></td></tr>
     265      <tr bgcolor="gray" ><td></td><th><a name="part-l7" /><small>skipping to change at</small><em> page 19, line 21</em></th><th> </th><th><a name="part-r7" /><small>skipping to change at</small><em> page 19, line 21</em></th><td></td></tr>
    308266      <tr><td class="lineno" valign="top"></td><td class="left">   representations for a response (the dimensions over which it might</td><td> </td><td class="right">   representations for a response (the dimensions over which it might</td><td class="lineno" valign="top"></td></tr>
    309267      <tr><td class="lineno" valign="top"></td><td class="left">   vary, such as language, content-coding, etc.) compared to various</td><td> </td><td class="right">   vary, such as language, content-coding, etc.) compared to various</td><td class="lineno" valign="top"></td></tr>
     
    316274      <tr><td class="lineno" valign="top"></td><td class="left">   describe to a user agent, or when the server desires to send its</td><td> </td><td class="right">   describe to a user agent, or when the server desires to send its</td><td class="lineno" valign="top"></td></tr>
    317275      <tr><td class="lineno" valign="top"></td><td class="left">   "best guess" to the user agent along with the first response (hoping</td><td> </td><td class="right">   "best guess" to the user agent along with the first response (hoping</td><td class="lineno" valign="top"></td></tr>
    318       <tr><td><a name="diff0016" /></td></tr>
     276      <tr><td><a name="diff0014" /></td></tr>
    319277      <tr><td class="lineno" valign="top"></td><td class="lblock">   to avoid the round<span class="delete"> </span>trip delay of a subsequent request if the "best</td><td> </td><td class="rblock">   to avoid the round<span class="insert">-</span>trip delay of a subsequent request if the "best</td><td class="lineno" valign="top"></td></tr>
    320278      <tr><td class="lineno" valign="top"></td><td class="left">   guess" is good enough for the user).  In order to improve the</td><td> </td><td class="right">   guess" is good enough for the user).  In order to improve the</td><td class="lineno" valign="top"></td></tr>
     
    329287      <tr><td class="lineno" valign="top"></td><td class="left">      intended use for the response (e.g., does the user want to view it</td><td> </td><td class="right">      intended use for the response (e.g., does the user want to view it</td><td class="lineno" valign="top"></td></tr>
    330288      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    331       <tr bgcolor="gray" ><td></td><th><a name="part-l9" /><small>skipping to change at</small><em> page 21, line 26</em></th><th> </th><th><a name="part-r9" /><small>skipping to change at</small><em> page 21, line 26</em></th><td></td></tr>
     289      <tr bgcolor="gray" ><td></td><th><a name="part-l8" /><small>skipping to change at</small><em> page 21, line 26</em></th><th> </th><th><a name="part-r8" /><small>skipping to change at</small><em> page 21, line 26</em></th><td></td></tr>
    332290      <tr><td class="lineno" valign="top"></td><td class="left">   example, a client can send conditional request header fields</td><td> </td><td class="right">   example, a client can send conditional request header fields</td><td class="lineno" valign="top"></td></tr>
    333291      <tr><td class="lineno" valign="top"></td><td class="left">   (Section 5.2) to make the requested action conditional on the current</td><td> </td><td class="right">   (Section 5.2) to make the requested action conditional on the current</td><td class="lineno" valign="top"></td></tr>
     
    340298      <tr><td class="lineno" valign="top"></td><td class="left">   applying semantics to a target resource in much the same way as</td><td> </td><td class="right">   applying semantics to a target resource in much the same way as</td><td class="lineno" valign="top"></td></tr>
    341299      <tr><td class="lineno" valign="top"></td><td class="left">   invoking a defined method on an identified object would apply</td><td> </td><td class="right">   invoking a defined method on an identified object would apply</td><td class="lineno" valign="top"></td></tr>
    342       <tr><td><a name="diff0017" /></td></tr>
     300      <tr><td><a name="diff0015" /></td></tr>
    343301      <tr><td class="lineno" valign="top"></td><td class="lblock">   semantics.  The method token is case<span class="delete">-</span>sensitive because it might be</td><td> </td><td class="rblock">   semantics.  The method token is case<span class="insert"> </span>sensitive because it might be</td><td class="lineno" valign="top"></td></tr>
    344302      <tr><td class="lineno" valign="top"></td><td class="left">   used as a gateway to object-based systems with case-sensitive method</td><td> </td><td class="right">   used as a gateway to object-based systems with case-sensitive method</td><td class="lineno" valign="top"></td></tr>
     
    346304      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    347305      <tr><td class="lineno" valign="top"></td><td class="left">   Unlike distributed objects, the standardized request methods in HTTP</td><td> </td><td class="right">   Unlike distributed objects, the standardized request methods in HTTP</td><td class="lineno" valign="top"></td></tr>
    348       <tr><td><a name="diff0018" /></td></tr>
     306      <tr><td><a name="diff0016" /></td></tr>
    349307      <tr><td class="lineno" valign="top"></td><td class="lblock">   are not resource<span class="delete">-</span>specific, since uniform interfaces provide for</td><td> </td><td class="rblock">   are not resource<span class="insert"> </span>specific, since uniform interfaces provide for</td><td class="lineno" valign="top"></td></tr>
    350308      <tr><td class="lineno" valign="top"></td><td class="left">   better visibility and reuse in network-based systems [REST].  Once</td><td> </td><td class="right">   better visibility and reuse in network-based systems [REST].  Once</td><td class="lineno" valign="top"></td></tr>
     
    355313      <tr><td class="lineno" valign="top"></td><td class="left">   This specification defines a number of standardized methods that are</td><td> </td><td class="right">   This specification defines a number of standardized methods that are</td><td class="lineno" valign="top"></td></tr>
    356314      <tr><td class="lineno" valign="top"></td><td class="left">   commonly used in HTTP, as outlined by the following table.  By</td><td> </td><td class="right">   commonly used in HTTP, as outlined by the following table.  By</td><td class="lineno" valign="top"></td></tr>
    357       <tr><td><a name="diff0019" /></td></tr>
     315      <tr><td><a name="diff0017" /></td></tr>
    358316      <tr><td class="lineno" valign="top"></td><td class="lblock">   convention, standardized methods are defined in all-uppercase <span class="delete">US-</span></td><td> </td><td class="rblock">   convention, standardized methods are defined in all-uppercase ASCII</td><td class="lineno" valign="top"></td></tr>
    359317      <tr><td class="lineno" valign="top"></td><td class="lblock">   ASCII letters.</td><td> </td><td class="rblock">   letters.</td><td class="lineno" valign="top"></td></tr>
     
    369327      <tr><td class="lineno" valign="top"></td><td class="left">   |         | request payload.                                |       |</td><td> </td><td class="right">   |         | request payload.                                |       |</td><td class="lineno" valign="top"></td></tr>
    370328      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    371       <tr bgcolor="gray" ><td></td><th><a name="part-l10" /><small>skipping to change at</small><em> page 22, line 31</em></th><th> </th><th><a name="part-r10" /><small>skipping to change at</small><em> page 22, line 31</em></th><td></td></tr>
     329      <tr bgcolor="gray" ><td></td><th><a name="part-l9" /><small>skipping to change at</small><em> page 22, line 31</em></th><th> </th><th><a name="part-r9" /><small>skipping to change at</small><em> page 22, line 31</em></th><td></td></tr>
    372330      <tr><td class="lineno" valign="top"></td><td class="left">   |         | target resource.                                |       |</td><td> </td><td class="right">   |         | target resource.                                |       |</td><td class="lineno" valign="top"></td></tr>
    373331      <tr><td class="lineno" valign="top"></td><td class="left">   | TRACE   | Perform a message loop-back test along the path | 4.3.8 |</td><td> </td><td class="right">   | TRACE   | Perform a message loop-back test along the path | 4.3.8 |</td><td class="lineno" valign="top"></td></tr>
     
    380338      <tr><td class="lineno" valign="top"></td><td class="left">   Additional methods, outside the scope of this specification, have</td><td> </td><td class="right">   Additional methods, outside the scope of this specification, have</td><td class="lineno" valign="top"></td></tr>
    381339      <tr><td class="lineno" valign="top"></td><td class="left">   been standardized for use in HTTP.  All such methods ought to be</td><td> </td><td class="right">   been standardized for use in HTTP.  All such methods ought to be</td><td class="lineno" valign="top"></td></tr>
    382       <tr><td><a name="diff0020" /></td></tr>
     340      <tr><td><a name="diff0018" /></td></tr>
    383341      <tr><td class="lineno" valign="top"></td><td class="lblock">   registered within the "Hypertext Transfer Protocol (HTTP) <span class="delete">Method</span></td><td> </td><td class="rblock">   registered within the "Hypertext Transfer Protocol (HTTP) <span class="insert">Method"</span></td><td class="lineno" valign="top"></td></tr>
    384342      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   Registry"</span> maintained by IANA, as defined in Section 8.1.</td><td> </td><td class="rblock"><span class="insert">   registry</span> maintained by IANA, as defined in Section 8.1.</td><td class="lineno" valign="top"></td></tr>
     
    394352      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    395353      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    396       <tr bgcolor="gray" ><td></td><th><a name="part-l11" /><small>skipping to change at</small><em> page 23, line 5</em></th><th> </th><th><a name="part-r11" /><small>skipping to change at</small><em> page 23, line 5</em></th><td></td></tr>
     354      <tr bgcolor="gray" ><td></td><th><a name="part-l10" /><small>skipping to change at</small><em> page 23, line 5</em></th><th> </th><th><a name="part-r10" /><small>skipping to change at</small><em> page 23, line 5</em></th><td></td></tr>
    397355      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    398356      <tr><td class="lineno" valign="top"></td><td class="left">4.2.1.  Safe Methods</td><td> </td><td class="right">4.2.1.  Safe Methods</td><td class="lineno" valign="top"></td></tr>
     
    405363      <tr><td class="lineno" valign="top"></td><td class="left">   property, or unusual burden on the origin server.</td><td> </td><td class="right">   property, or unusual burden on the origin server.</td><td class="lineno" valign="top"></td></tr>
    406364      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    407       <tr><td><a name="diff0021" /></td></tr>
     365      <tr><td><a name="diff0019" /></td></tr>
    408366      <tr><td class="lineno" valign="top"></td><td class="lblock">   This definition of safe method<span class="delete">s</span> does not prevent an implementation</td><td> </td><td class="rblock">   This definition of safe method does not prevent an implementation</td><td class="lineno" valign="top"></td></tr>
    409367      <tr><td class="lineno" valign="top"></td><td class="left">   from including behavior that is potentially harmful, that is not</td><td> </td><td class="right">   from including behavior that is potentially harmful, that is not</td><td class="lineno" valign="top"></td></tr>
     
    418376      <tr><td class="lineno" valign="top"></td><td class="left">   effect of charging an advertising account.</td><td> </td><td class="right">   effect of charging an advertising account.</td><td class="lineno" valign="top"></td></tr>
    419377      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    420       <tr bgcolor="gray" ><td></td><th><a name="part-l12" /><small>skipping to change at</small><em> page 34, line 14</em></th><th> </th><th><a name="part-r12" /><small>skipping to change at</small><em> page 34, line 14</em></th><td></td></tr>
     378      <tr bgcolor="gray" ><td></td><th><a name="part-l11" /><small>skipping to change at</small><em> page 34, line 14</em></th><th> </th><th><a name="part-r11" /><small>skipping to change at</small><em> page 34, line 14</em></th><td></td></tr>
    421379      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    422380      <tr><td class="lineno" valign="top"></td><td class="left">5.1.1.  Expect</td><td> </td><td class="right">5.1.1.  Expect</td><td class="lineno" valign="top"></td></tr>
     
    429387      <tr><td class="lineno" valign="top"></td><td class="left">     Expect  = "100-continue"</td><td> </td><td class="right">     Expect  = "100-continue"</td><td class="lineno" valign="top"></td></tr>
    430388      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    431       <tr><td><a name="diff0022" /></td></tr>
     389      <tr><td><a name="diff0020" /></td></tr>
    432390      <tr><td class="lineno" valign="top"></td><td class="lblock">   The Expect field-value is case<span class="delete">-</span>insensitive.</td><td> </td><td class="rblock">   The Expect field-value is case<span class="insert"> </span>insensitive.</td><td class="lineno" valign="top"></td></tr>
    433391      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     
    442400      <tr><td class="lineno" valign="top"></td><td class="left">   success, redirect, or error response.  This allows the client to wait</td><td> </td><td class="right">   success, redirect, or error response.  This allows the client to wait</td><td class="lineno" valign="top"></td></tr>
    443401      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    444       <tr bgcolor="gray" ><td></td><th><a name="part-l13" /><small>skipping to change at</small><em> page 44, line 30</em></th><th> </th><th><a name="part-r13" /><small>skipping to change at</small><em> page 44, line 30</em></th><td></td></tr>
     402      <tr bgcolor="gray" ><td></td><th><a name="part-l12" /><small>skipping to change at</small><em> page 44, line 30</em></th><th> </th><th><a name="part-r12" /><small>skipping to change at</small><em> page 44, line 30</em></th><td></td></tr>
    445403      <tr><td class="lineno" valign="top"></td><td class="left">   +-------------------+---------------+</td><td> </td><td class="right">   +-------------------+---------------+</td><td class="lineno" valign="top"></td></tr>
    446404      <tr><td class="lineno" valign="top"></td><td class="left">   | From              | Section 5.5.1 |</td><td> </td><td class="right">   | From              | Section 5.5.1 |</td><td class="lineno" valign="top"></td></tr>
     
    453411      <tr><td class="lineno" valign="top"></td><td class="left">   The "From" header field contains an Internet email address for a</td><td> </td><td class="right">   The "From" header field contains an Internet email address for a</td><td class="lineno" valign="top"></td></tr>
    454412      <tr><td class="lineno" valign="top"></td><td class="left">   human user who controls the requesting user agent.  The address ought</td><td> </td><td class="right">   human user who controls the requesting user agent.  The address ought</td><td class="lineno" valign="top"></td></tr>
    455       <tr><td><a name="diff0023" /></td></tr>
     413      <tr><td><a name="diff0021" /></td></tr>
    456414      <tr><td class="lineno" valign="top"></td><td class="lblock">   to be machine<span class="delete">-</span>usable, as defined by "mailbox" in Section 3.4 of</td><td> </td><td class="rblock">   to be machine<span class="insert"> </span>usable, as defined by "mailbox" in Section 3.4 of</td><td class="lineno" valign="top"></td></tr>
    457415      <tr><td class="lineno" valign="top"></td><td class="left">   [RFC5322]:</td><td> </td><td class="right">   [RFC5322]:</td><td class="lineno" valign="top"></td></tr>
     
    466424      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    467425      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    468       <tr bgcolor="gray" ><td></td><th><a name="part-l14" /><small>skipping to change at</small><em> page 45, line 31</em></th><th> </th><th><a name="part-r14" /><small>skipping to change at</small><em> page 45, line 31</em></th><td></td></tr>
    469       <tr><td class="lineno" valign="top"></td><td class="left">   denying links from other sites (so-called "deep linking") or</td><td> </td><td class="right">   denying links from other sites (so-called "deep linking") or</td><td class="lineno" valign="top"></td></tr>
     426      <tr bgcolor="gray" ><td></td><th><a name="part-l13" /><small>skipping to change at</small><em> page 45, line 32</em></th><th> </th><th><a name="part-r13" /><small>skipping to change at</small><em> page 45, line 32</em></th><td></td></tr>
    470427      <tr><td class="lineno" valign="top"></td><td class="left">   restricting cross-site request forgery (CSRF), but not all requests</td><td> </td><td class="right">   restricting cross-site request forgery (CSRF), but not all requests</td><td class="lineno" valign="top"></td></tr>
    471428      <tr><td class="lineno" valign="top"></td><td class="left">   contain it.</td><td> </td><td class="right">   contain it.</td><td class="lineno" valign="top"></td></tr>
     
    477434      <tr><td class="lineno" valign="top"></td><td class="left">   If the target URI was obtained from a source that does not have its</td><td> </td><td class="right">   If the target URI was obtained from a source that does not have its</td><td class="lineno" valign="top"></td></tr>
    478435      <tr><td class="lineno" valign="top"></td><td class="left">   own URI (e.g., input from the user keyboard, or an entry within the</td><td> </td><td class="right">   own URI (e.g., input from the user keyboard, or an entry within the</td><td class="lineno" valign="top"></td></tr>
    479       <tr><td><a name="diff0024" /></td></tr>
    480       <tr><td class="lineno" valign="top"></td><td class="lblock">   user's bookmarks/favorites), the user agent MUST either exclude</td><td> </td><td class="rblock">   user's bookmarks/favorites), the user agent MUST either exclude<span class="insert"> the</span></td><td class="lineno" valign="top"></td></tr>
    481       <tr><td class="lineno" valign="top"></td><td class="left">   Referer or send it with a value of "about:blank".</td><td> </td><td class="right">   Referer or send it with a value of "about:blank".</td><td class="lineno" valign="top"></td></tr>
     436      <tr><td class="lineno" valign="top"></td><td class="left">   user's bookmarks/favorites), the user agent MUST either exclude the</td><td> </td><td class="right">   user's bookmarks/favorites), the user agent MUST either exclude the</td><td class="lineno" valign="top"></td></tr>
     437      <tr><td><a name="diff0022" /></td></tr>
     438      <tr><td class="lineno" valign="top"></td><td class="lblock">   Referer <span class="delete">field </span>or send it with a value of "about:blank".</td><td> </td><td class="rblock">   Referer or send it with a value of "about:blank".</td><td class="lineno" valign="top"></td></tr>
    482439      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    483440      <tr><td class="lineno" valign="top"></td><td class="left">   The Referer field has the potential to reveal information about the</td><td> </td><td class="right">   The Referer field has the potential to reveal information about the</td><td class="lineno" valign="top"></td></tr>
     
    489446      <tr><td class="lineno" valign="top"></td><td class="left">   Referer header field when the referring resource is a local "file" or</td><td> </td><td class="right">   Referer header field when the referring resource is a local "file" or</td><td class="lineno" valign="top"></td></tr>
    490447      <tr><td class="lineno" valign="top"></td><td class="left">   "data" URI.  A user agent MUST NOT send a Referer header field in an</td><td> </td><td class="right">   "data" URI.  A user agent MUST NOT send a Referer header field in an</td><td class="lineno" valign="top"></td></tr>
    491       <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    492       <tr bgcolor="gray" ><td></td><th><a name="part-l15" /><small>skipping to change at</small><em> page 46, line 15</em></th><th> </th><th><a name="part-r15" /><small>skipping to change at</small><em> page 46, line 15</em></th><td></td></tr>
     448      <tr><td class="lineno" valign="top"></td><td class="left">   unsecured HTTP request if the referring page was received with a</td><td> </td><td class="right">   unsecured HTTP request if the referring page was received with a</td><td class="lineno" valign="top"></td></tr>
     449      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
     450      <tr bgcolor="gray" ><td></td><th><a name="part-l14" /><small>skipping to change at</small><em> page 46, line 15</em></th><th> </th><th><a name="part-r14" /><small>skipping to change at</small><em> page 46, line 15</em></th><td></td></tr>
    493451      <tr><td class="lineno" valign="top"></td><td class="left">   pseudonyms or truncating the query and/or path components.  An</td><td> </td><td class="right">   pseudonyms or truncating the query and/or path components.  An</td><td class="lineno" valign="top"></td></tr>
    494452      <tr><td class="lineno" valign="top"></td><td class="left">   intermediary SHOULD NOT modify or delete the Referer header field</td><td> </td><td class="right">   intermediary SHOULD NOT modify or delete the Referer header field</td><td class="lineno" valign="top"></td></tr>
     
    501459      <tr><td class="lineno" valign="top"></td><td class="left">   agent originating the request, which is often used by servers to help</td><td> </td><td class="right">   agent originating the request, which is often used by servers to help</td><td class="lineno" valign="top"></td></tr>
    502460      <tr><td class="lineno" valign="top"></td><td class="left">   identify the scope of reported interoperability problems, to work</td><td> </td><td class="right">   identify the scope of reported interoperability problems, to work</td><td class="lineno" valign="top"></td></tr>
    503       <tr><td><a name="diff0025" /></td></tr>
     461      <tr><td><a name="diff0023" /></td></tr>
    504462      <tr><td class="lineno" valign="top"></td><td class="lblock">   around or tailor responses to avoid particular user<span class="delete"> </span>agent</td><td> </td><td class="rblock">   around or tailor responses to avoid particular user<span class="insert">-</span>agent</td><td class="lineno" valign="top"></td></tr>
    505463      <tr><td class="lineno" valign="top"></td><td class="left">   limitations, and for analytics regarding browser or operating system</td><td> </td><td class="right">   limitations, and for analytics regarding browser or operating system</td><td class="lineno" valign="top"></td></tr>
     
    511469      <tr><td class="lineno" valign="top"></td><td class="left">   The User-Agent field-value consists of one or more product</td><td> </td><td class="right">   The User-Agent field-value consists of one or more product</td><td class="lineno" valign="top"></td></tr>
    512470      <tr><td class="lineno" valign="top"></td><td class="left">   identifiers, each followed by zero or more comments (Section 3.2 of</td><td> </td><td class="right">   identifiers, each followed by zero or more comments (Section 3.2 of</td><td class="lineno" valign="top"></td></tr>
    513       <tr><td><a name="diff0026" /></td></tr>
     471      <tr><td><a name="diff0024" /></td></tr>
    514472      <tr><td class="lineno" valign="top"></td><td class="lblock">   [RFC7230]), which together identify the user<span class="delete"> </span>agent software and its</td><td> </td><td class="rblock">   [RFC7230]), which together identify the user<span class="insert">-</span>agent software and its</td><td class="lineno" valign="top"></td></tr>
    515473      <tr><td class="lineno" valign="top"></td><td class="left">   significant subproducts.  By convention, the product identifiers are</td><td> </td><td class="right">   significant subproducts.  By convention, the product identifiers are</td><td class="lineno" valign="top"></td></tr>
    516474      <tr><td class="lineno" valign="top"></td><td class="left">   listed in decreasing order of their significance for identifying the</td><td> </td><td class="right">   listed in decreasing order of their significance for identifying the</td><td class="lineno" valign="top"></td></tr>
    517       <tr><td><a name="diff0027" /></td></tr>
     475      <tr><td><a name="diff0025" /></td></tr>
    518476      <tr><td class="lineno" valign="top"></td><td class="lblock">   user<span class="delete"> </span>agent software.  Each product identifier consists of a name and</td><td> </td><td class="rblock">   user<span class="insert">-</span>agent software.  Each product identifier consists of a name and</td><td class="lineno" valign="top"></td></tr>
    519477      <tr><td class="lineno" valign="top"></td><td class="left">   optional version.</td><td> </td><td class="right">   optional version.</td><td class="lineno" valign="top"></td></tr>
     
    528486      <tr><td class="lineno" valign="top"></td><td class="left">   version that is not a version identifier (i.e., successive versions</td><td> </td><td class="right">   version that is not a version identifier (i.e., successive versions</td><td class="lineno" valign="top"></td></tr>
    529487      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    530       <tr bgcolor="gray" ><td></td><th><a name="part-l16" /><small>skipping to change at</small><em> page 47, line 9</em></th><th> </th><th><a name="part-r16" /><small>skipping to change at</small><em> page 47, line 9</em></th><td></td></tr>
     488      <tr bgcolor="gray" ><td></td><th><a name="part-l15" /><small>skipping to change at</small><em> page 47, line 9</em></th><th> </th><th><a name="part-r15" /><small>skipping to change at</small><em> page 47, line 9</em></th><td></td></tr>
    531489      <tr><td class="lineno" valign="top"></td><td class="left">   subproducts by third parties.  Overly long and detailed User-Agent</td><td> </td><td class="right">   subproducts by third parties.  Overly long and detailed User-Agent</td><td class="lineno" valign="top"></td></tr>
    532490      <tr><td class="lineno" valign="top"></td><td class="left">   field values increase request latency and the risk of a user being</td><td> </td><td class="right">   field values increase request latency and the risk of a user being</td><td class="lineno" valign="top"></td></tr>
     
    539497      <tr><td class="lineno" valign="top"></td><td class="left">   that the user intentionally desires to see responses tailored for</td><td> </td><td class="right">   that the user intentionally desires to see responses tailored for</td><td class="lineno" valign="top"></td></tr>
    540498      <tr><td class="lineno" valign="top"></td><td class="left">   that identified user agent, even if they might not work as well for</td><td> </td><td class="right">   that identified user agent, even if they might not work as well for</td><td class="lineno" valign="top"></td></tr>
    541       <tr><td><a name="diff0028" /></td></tr>
     499      <tr><td><a name="diff0026" /></td></tr>
    542500      <tr><td class="lineno" valign="top"></td><td class="lblock">   the actual user agent being <span class="delete">us</span>ed.</td><td> </td><td class="rblock">   the actual user agent being <span class="insert">implement</span>ed.</td><td class="lineno" valign="top"></td></tr>
    543501      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     
    552510      <tr><td class="lineno" valign="top"></td><td class="left">   understand the class of any status code, as indicated by the first</td><td> </td><td class="right">   understand the class of any status code, as indicated by the first</td><td class="lineno" valign="top"></td></tr>
    553511      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    554       <tr bgcolor="gray" ><td></td><th><a name="part-l17" /><small>skipping to change at</small><em> page 56, line 6</em></th><th> </th><th><a name="part-r17" /><small>skipping to change at</small><em> page 56, line 6</em></th><td></td></tr>
     512      <tr bgcolor="gray" ><td></td><th><a name="part-l16" /><small>skipping to change at</small><em> page 56, line 6</em></th><th> </th><th><a name="part-r16" /><small>skipping to change at</small><em> page 56, line 6</em></th><td></td></tr>
    555513      <tr><td class="lineno" valign="top"></td><td class="left">   this specification because HTTP tries to remain orthogonal to the</td><td> </td><td class="right">   this specification because HTTP tries to remain orthogonal to the</td><td class="lineno" valign="top"></td></tr>
    556514      <tr><td class="lineno" valign="top"></td><td class="left">   definition of its payloads.  In practice, the representation is</td><td> </td><td class="right">   definition of its payloads.  In practice, the representation is</td><td class="lineno" valign="top"></td></tr>
     
    563521      <tr><td class="lineno" valign="top"></td><td class="left">   Section 4.2.2 of [RFC7234]).</td><td> </td><td class="right">   Section 4.2.2 of [RFC7234]).</td><td class="lineno" valign="top"></td></tr>
    564522      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    565       <tr><td><a name="diff0029" /></td></tr>
     523      <tr><td><a name="diff0027" /></td></tr>
    566524      <tr><td class="lineno" valign="top"></td><td class="lblock">      Note: The original proposal for the 300 <span class="delete">status code</span> defined the</td><td> </td><td class="rblock">      Note: The original proposal for the 300 <span class="insert">response</span> defined the URI</td><td class="lineno" valign="top"></td></tr>
    567525      <tr><td class="lineno" valign="top"></td><td class="lblock">      URI header field as providing a list of alternative</td><td> </td><td class="rblock">      header field as providing a list of alternative representations,</td><td class="lineno" valign="top"></td></tr>
     
    583541      <tr><td class="lineno" valign="top"></td><td class="left">   references sent by the server, where possible.</td><td> </td><td class="right">   references sent by the server, where possible.</td><td class="lineno" valign="top"></td></tr>
    584542      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    585       <tr bgcolor="gray" ><td></td><th><a name="part-l18" /><small>skipping to change at</small><em> page 58, line 23</em></th><th> </th><th><a name="part-r18" /><small>skipping to change at</small><em> page 58, line 23</em></th><td></td></tr>
     543      <tr bgcolor="gray" ><td></td><th><a name="part-l17" /><small>skipping to change at</small><em> page 58, line 23</em></th><th> </th><th><a name="part-r17" /><small>skipping to change at</small><em> page 58, line 23</em></th><td></td></tr>
    586544      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    587545      <tr><td class="lineno" valign="top"></td><td class="left">   The server SHOULD generate a Location header field in the response</td><td> </td><td class="right">   The server SHOULD generate a Location header field in the response</td><td class="lineno" valign="top"></td></tr>
     
    594552      <tr><td class="lineno" valign="top"></td><td class="left">      does not allow changing the request method from POST to GET.  This</td><td> </td><td class="right">      does not allow changing the request method from POST to GET.  This</td><td class="lineno" valign="top"></td></tr>
    595553      <tr><td class="lineno" valign="top"></td><td class="left">      specification defines no equivalent counterpart for 301 (Moved</td><td> </td><td class="right">      specification defines no equivalent counterpart for 301 (Moved</td><td class="lineno" valign="top"></td></tr>
    596       <tr><td><a name="diff0030" /></td></tr>
     554      <tr><td><a name="diff0028" /></td></tr>
    597555      <tr><td class="lineno" valign="top"></td><td class="lblock">      Permanently) ([RFC7238]<span class="delete">, however,</span> defines the status code 308</td><td> </td><td class="rblock">      Permanently) ([RFC7238]<span class="insert">; however, it</span> defines the status code 308</td><td class="lineno" valign="top"></td></tr>
    598556      <tr><td class="lineno" valign="top"></td><td class="left">      (Permanent Redirect) for this purpose).</td><td> </td><td class="right">      (Permanent Redirect) for this purpose).</td><td class="lineno" valign="top"></td></tr>
     
    607565      <tr><td class="lineno" valign="top"></td><td class="left">   User agents SHOULD display any included representation to the user.</td><td> </td><td class="right">   User agents SHOULD display any included representation to the user.</td><td class="lineno" valign="top"></td></tr>
    608566      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    609       <tr bgcolor="gray" ><td></td><th><a name="part-l19" /><small>skipping to change at</small><em> page 60, line 13</em></th><th> </th><th><a name="part-r19" /><small>skipping to change at</small><em> page 60, line 13</em></th><td></td></tr>
     567      <tr bgcolor="gray" ><td></td><th><a name="part-l18" /><small>skipping to change at</small><em> page 60, line 13</em></th><th> </th><th><a name="part-r18" /><small>skipping to change at</small><em> page 60, line 13</em></th><td></td></tr>
    610568      <tr><td class="lineno" valign="top"></td><td class="left">   from which the user or user agent can choose the one most</td><td> </td><td class="right">   from which the user or user agent can choose the one most</td><td class="lineno" valign="top"></td></tr>
    611569      <tr><td class="lineno" valign="top"></td><td class="left">   appropriate.  A user agent MAY automatically select the most</td><td> </td><td class="right">   appropriate.  A user agent MAY automatically select the most</td><td class="lineno" valign="top"></td></tr>
     
    618576      <tr><td class="lineno" valign="top"></td><td class="left">   The 408 (Request Timeout) status code indicates that the server did</td><td> </td><td class="right">   The 408 (Request Timeout) status code indicates that the server did</td><td class="lineno" valign="top"></td></tr>
    619577      <tr><td class="lineno" valign="top"></td><td class="left">   not receive a complete request message within the time that it was</td><td> </td><td class="right">   not receive a complete request message within the time that it was</td><td class="lineno" valign="top"></td></tr>
    620       <tr><td><a name="diff0031" /></td></tr>
     578      <tr><td><a name="diff0029" /></td></tr>
    621579      <tr><td class="lineno" valign="top"></td><td class="lblock">   prepared to wait.  A server SHOULD send the <span class="delete">"close"</span> connection option</td><td> </td><td class="rblock">   prepared to wait.  A server SHOULD send the <span class="insert">close</span> connection option</td><td class="lineno" valign="top"></td></tr>
    622580      <tr><td class="lineno" valign="top"></td><td class="left">   (Section 6.1 of [RFC7230]) in the response, since 408 implies that</td><td> </td><td class="right">   (Section 6.1 of [RFC7230]) in the response, since 408 implies that</td><td class="lineno" valign="top"></td></tr>
     
    631589      <tr><td class="lineno" valign="top"></td><td class="left">   resource.  This code is used in situations where the user might be</td><td> </td><td class="right">   resource.  This code is used in situations where the user might be</td><td class="lineno" valign="top"></td></tr>
    632590      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    633       <tr bgcolor="gray" ><td></td><th><a name="part-l20" /><small>skipping to change at</small><em> page 66, line 9</em></th><th> </th><th><a name="part-r20" /><small>skipping to change at</small><em> page 66, line 9</em></th><td></td></tr>
     591      <tr bgcolor="gray" ><td></td><th><a name="part-l19" /><small>skipping to change at</small><em> page 66, line 9</em></th><th> </th><th><a name="part-r19" /><small>skipping to change at</small><em> page 66, line 9</em></th><td></td></tr>
    634592      <tr><td class="lineno" valign="top"></td><td class="left">   to be in UTC.  A sender that generates HTTP-date values from a local</td><td> </td><td class="right">   to be in UTC.  A sender that generates HTTP-date values from a local</td><td class="lineno" valign="top"></td></tr>
    635593      <tr><td class="lineno" valign="top"></td><td class="left">   clock ought to use NTP ([RFC5905]) or some similar protocol to</td><td> </td><td class="right">   clock ought to use NTP ([RFC5905]) or some similar protocol to</td><td class="lineno" valign="top"></td></tr>
     
    642600      <tr><td class="lineno" valign="top"></td><td class="left">     ; defined in Section 3.3 of [RFC5322]</td><td> </td><td class="right">     ; defined in Section 3.3 of [RFC5322]</td><td class="lineno" valign="top"></td></tr>
    643601      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    644       <tr><td><a name="diff0032" /></td></tr>
     602      <tr><td><a name="diff0030" /></td></tr>
    645603      <tr><td class="lineno" valign="top"></td><td class="lblock">     day-name     = %x4D.6F.6E ; "Mon", <span class="delete">case-sensitive</span></td><td> </td><td class="rblock">     day-name     = %x4D.6F.6E ; "Mon", <span class="insert">case sensitive</span></td><td class="lineno" valign="top"></td></tr>
    646604      <tr><td class="lineno" valign="top"></td><td class="lblock">                  / %x54.75.65 ; "Tue", <span class="delete">case-sensitive</span></td><td> </td><td class="rblock">                  / %x54.75.65 ; "Tue", <span class="insert">case sensitive</span></td><td class="lineno" valign="top"></td></tr>
     
    655613      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    656614      <tr><td class="lineno" valign="top"></td><td class="left">     day          = 2DIGIT</td><td> </td><td class="right">     day          = 2DIGIT</td><td class="lineno" valign="top"></td></tr>
    657       <tr><td><a name="diff0033" /></td></tr>
     615      <tr><td><a name="diff0031" /></td></tr>
    658616      <tr><td class="lineno" valign="top"></td><td class="lblock">     month        = %x4A.61.6E ; "Jan", <span class="delete">case-sensitive</span></td><td> </td><td class="rblock">     month        = %x4A.61.6E ; "Jan", <span class="insert">case sensitive</span></td><td class="lineno" valign="top"></td></tr>
    659617      <tr><td class="lineno" valign="top"></td><td class="lblock">                  / %x46.65.62 ; "Feb", <span class="delete">case-sensitive</span></td><td> </td><td class="rblock">                  / %x46.65.62 ; "Feb", <span class="insert">case sensitive</span></td><td class="lineno" valign="top"></td></tr>
     
    670628      <tr><td class="lineno" valign="top"></td><td class="left">     year         = 4DIGIT</td><td> </td><td class="right">     year         = 4DIGIT</td><td class="lineno" valign="top"></td></tr>
    671629      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    672       <tr><td><a name="diff0034" /></td></tr>
     630      <tr><td><a name="diff0032" /></td></tr>
    673631      <tr><td class="lineno" valign="top"></td><td class="lblock">     GMT          = %x47.4D.54 ; "GMT", case<span class="delete">-</span>sensitive</td><td> </td><td class="rblock">     GMT          = %x47.4D.54 ; "GMT", case<span class="insert"> </span>sensitive</td><td class="lineno" valign="top"></td></tr>
    674632      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     
    687645      <tr><td class="lineno" valign="top"></td><td class="left">                  ; e.g., 02-Jun-82</td><td> </td><td class="right">                  ; e.g., 02-Jun-82</td><td class="lineno" valign="top"></td></tr>
    688646      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    689       <tr><td><a name="diff0035" /></td></tr>
     647      <tr><td><a name="diff0033" /></td></tr>
    690648      <tr><td class="lineno" valign="top"></td><td class="lblock">     day-name-l   = %x4D.6F.6E.64.61.79    ; "Monday", <span class="delete">case-sensitive</span></td><td> </td><td class="rblock">     day-name-l   = %x4D.6F.6E.64.61.79    ; "Monday", <span class="insert">case sensitive</span></td><td class="lineno" valign="top"></td></tr>
    691649      <tr><td class="lineno" valign="top"></td><td class="lblock">            / %x54.75.65.73.64.61.79       ; "Tuesday", <span class="delete">case-sensitive</span></td><td> </td><td class="rblock">            / %x54.75.65.73.64.61.79       ; "Tuesday", <span class="insert">case sensitive</span></td><td class="lineno" valign="top"></td></tr>
     
    706664      <tr><td class="lineno" valign="top"></td><td class="left">   constructs with the corresponding name ([RFC5322], Section 3.3).</td><td> </td><td class="right">   constructs with the corresponding name ([RFC5322], Section 3.3).</td><td class="lineno" valign="top"></td></tr>
    707665      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    708       <tr bgcolor="gray" ><td></td><th><a name="part-l21" /><small>skipping to change at</small><em> page 70, line 30</em></th><th> </th><th><a name="part-r21" /><small>skipping to change at</small><em> page 70, line 30</em></th><td></td></tr>
     666      <tr bgcolor="gray" ><td></td><th><a name="part-l20" /><small>skipping to change at</small><em> page 70, line 30</em></th><th> </th><th><a name="part-r20" /><small>skipping to change at</small><em> page 70, line 30</em></th><td></td></tr>
    709667      <tr><td class="lineno" valign="top"></td><td class="left">     Retry-After: 120</td><td> </td><td class="right">     Retry-After: 120</td><td class="lineno" valign="top"></td></tr>
    710668      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     
    717675      <tr><td class="lineno" valign="top"></td><td class="left">   request target, might influence the origin server's process for</td><td> </td><td class="right">   request target, might influence the origin server's process for</td><td class="lineno" valign="top"></td></tr>
    718676      <tr><td class="lineno" valign="top"></td><td class="left">   selecting and representing this response.  The value consists of</td><td> </td><td class="right">   selecting and representing this response.  The value consists of</td><td class="lineno" valign="top"></td></tr>
    719       <tr><td><a name="diff0036" /></td></tr>
     677      <tr><td><a name="diff0034" /></td></tr>
    720678      <tr><td class="lineno" valign="top"></td><td class="lblock">   either a single asterisk ("*") or a list of header field names (case<span class="delete">-</span></td><td> </td><td class="rblock">   either a single asterisk ("*") or a list of header field names (case</td><td class="lineno" valign="top"></td></tr>
    721679      <tr><td class="lineno" valign="top"></td><td class="left">   insensitive).</td><td> </td><td class="right">   insensitive).</td><td class="lineno" valign="top"></td></tr>
     
    730688      <tr><td class="lineno" valign="top"></td><td class="left">   the request to the origin server.  A proxy MUST NOT generate a Vary</td><td> </td><td class="right">   the request to the origin server.  A proxy MUST NOT generate a Vary</td><td class="lineno" valign="top"></td></tr>
    731689      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    732       <tr bgcolor="gray" ><td></td><th><a name="part-l22" /><small>skipping to change at</small><em> page 71, line 22</em></th><th> </th><th><a name="part-r22" /><small>skipping to change at</small><em> page 71, line 22</em></th><td></td></tr>
     690      <tr bgcolor="gray" ><td></td><th><a name="part-l21" /><small>skipping to change at</small><em> page 71, line 22</em></th><th> </th><th><a name="part-r21" /><small>skipping to change at</small><em> page 71, line 22</em></th><td></td></tr>
    733691      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    734692      <tr><td class="lineno" valign="top"></td><td class="left">   An origin server might send Vary with a list of fields for two</td><td> </td><td class="right">   An origin server might send Vary with a list of fields for two</td><td class="lineno" valign="top"></td></tr>
     
    741699      <tr><td class="lineno" valign="top"></td><td class="left">       required to match a new request to the stored cache entry.</td><td> </td><td class="right">       required to match a new request to the stored cache entry.</td><td class="lineno" valign="top"></td></tr>
    742700      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    743       <tr><td><a name="diff0037" /></td></tr>
     701      <tr><td><a name="diff0035" /></td></tr>
    744702      <tr><td class="lineno" valign="top"></td><td class="lblock">   2.  To inform user<span class="delete"> </span>agent recipients that this response is subject to</td><td> </td><td class="rblock">   2.  To inform user<span class="insert">-</span>agent recipients that this response is subject to</td><td class="lineno" valign="top"></td></tr>
    745703      <tr><td class="lineno" valign="top"></td><td class="left">       content negotiation (Section 5.3) and that a different</td><td> </td><td class="right">       content negotiation (Section 5.3) and that a different</td><td class="lineno" valign="top"></td></tr>
     
    754712      <tr><td class="lineno" valign="top"></td><td class="left">   configured to prevent cache transparency.  For example, there is no</td><td> </td><td class="right">   configured to prevent cache transparency.  For example, there is no</td><td class="lineno" valign="top"></td></tr>
    755713      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    756       <tr bgcolor="gray" ><td></td><th><a name="part-l23" /><small>skipping to change at</small><em> page 74, line 7</em></th><th> </th><th><a name="part-r23" /><small>skipping to change at</small><em> page 74, line 7</em></th><td></td></tr>
     714      <tr bgcolor="gray" ><td></td><th><a name="part-l22" /><small>skipping to change at</small><em> page 74, line 7</em></th><th> </th><th><a name="part-r22" /><small>skipping to change at</small><em> page 74, line 7</em></th><td></td></tr>
    757715      <tr><td class="lineno" valign="top"></td><td class="left">   needlessly fine-grained detail and SHOULD limit the addition of</td><td> </td><td class="right">   needlessly fine-grained detail and SHOULD limit the addition of</td><td class="lineno" valign="top"></td></tr>
    758716      <tr><td class="lineno" valign="top"></td><td class="left">   subproducts by third parties.  Overly long and detailed Server field</td><td> </td><td class="right">   subproducts by third parties.  Overly long and detailed Server field</td><td class="lineno" valign="top"></td></tr>
     
    765723      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    766724      <tr><td class="lineno" valign="top"></td><td class="left">   The "Hypertext Transfer Protocol (HTTP) Method Registry" defines the</td><td> </td><td class="right">   The "Hypertext Transfer Protocol (HTTP) Method Registry" defines the</td><td class="lineno" valign="top"></td></tr>
    767       <tr><td><a name="diff0038" /></td></tr>
     725      <tr><td><a name="diff0036" /></td></tr>
    768726      <tr><td class="lineno" valign="top"></td><td class="lblock">   namespace for the request method token (Section 4).  The <span class="delete">method</span></td><td> </td><td class="rblock">   namespace for the request method token (Section 4).  The <span class="insert">"HTTP Method</span></td><td class="lineno" valign="top"></td></tr>
    769727      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   registry</span> has been created and is now maintained at</td><td> </td><td class="rblock"><span class="insert">   Registry"</span> has been created and is now maintained at</td><td class="lineno" valign="top"></td></tr>
     
    779737      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    780738      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    781       <tr bgcolor="gray" ><td></td><th><a name="part-l24" /><small>skipping to change at</small><em> page 74, line 44</em></th><th> </th><th><a name="part-r24" /><small>skipping to change at</small><em> page 74, line 44</em></th><td></td></tr>
     739      <tr bgcolor="gray" ><td></td><th><a name="part-l23" /><small>skipping to change at</small><em> page 74, line 44</em></th><th> </th><th><a name="part-r23" /><small>skipping to change at</small><em> page 74, line 44</em></th><td></td></tr>
    782740      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    783741      <tr><td class="lineno" valign="top"></td><td class="left">   Since message parsing (Section 3.3 of [RFC7230]) needs to be</td><td> </td><td class="right">   Since message parsing (Section 3.3 of [RFC7230]) needs to be</td><td class="lineno" valign="top"></td></tr>
     
    790748      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    791749      <tr><td class="lineno" valign="top"></td><td class="left">   A new method definition needs to indicate whether it is safe</td><td> </td><td class="right">   A new method definition needs to indicate whether it is safe</td><td class="lineno" valign="top"></td></tr>
    792       <tr><td><a name="diff0039" /></td></tr>
     750      <tr><td><a name="diff0037" /></td></tr>
    793751      <tr><td class="lineno" valign="top"></td><td class="lblock">   (Section 4.2.1), idempotent (Section 4.2.2), cacheable</td><td> </td><td class="rblock">   (Section 4.2.1), idempotent (Section 4.2.2), <span class="insert">or</span> cacheable</td><td class="lineno" valign="top"></td></tr>
    794752      <tr><td class="lineno" valign="top"></td><td class="lblock">   (Section <span class="delete">4.2.3),</span> what semantics are to be associated with the payload</td><td> </td><td class="rblock">   (Section <span class="insert">4.2.3).  It needs to indicate</span> what semantics are to be</td><td class="lineno" valign="top"></td></tr>
     
    813771      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    814772      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    815       <tr bgcolor="gray" ><td></td><th><a name="part-l25" /><small>skipping to change at</small><em> page 75, line 34</em></th><th> </th><th><a name="part-r25" /><small>skipping to change at</small><em> page 75, line 34</em></th><td></td></tr>
     773      <tr bgcolor="gray" ><td></td><th><a name="part-l24" /><small>skipping to change at</small><em> page 75, line 34</em></th><th> </th><th><a name="part-r24" /><small>skipping to change at</small><em> page 75, line 34</em></th><td></td></tr>
    816774      <tr><td class="lineno" valign="top"></td><td class="left">   | OPTIONS | yes  | yes        | Section 4.3.7 |</td><td> </td><td class="right">   | OPTIONS | yes  | yes        | Section 4.3.7 |</td><td class="lineno" valign="top"></td></tr>
    817775      <tr><td class="lineno" valign="top"></td><td class="left">   | POST    | no   | no         | Section 4.3.3 |</td><td> </td><td class="right">   | POST    | no   | no         | Section 4.3.3 |</td><td class="lineno" valign="top"></td></tr>
     
    824782      <tr><td class="lineno" valign="top"></td><td class="left">   The "Hypertext Transfer Protocol (HTTP) Status Code Registry" defines</td><td> </td><td class="right">   The "Hypertext Transfer Protocol (HTTP) Status Code Registry" defines</td><td class="lineno" valign="top"></td></tr>
    825783      <tr><td class="lineno" valign="top"></td><td class="left">   the namespace for the response status-code token (Section 6).  The</td><td> </td><td class="right">   the namespace for the response status-code token (Section 6).  The</td><td class="lineno" valign="top"></td></tr>
    826       <tr><td><a name="diff0040" /></td></tr>
     784      <tr><td><a name="diff0038" /></td></tr>
    827785      <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">status code</span> registry is maintained at</td><td> </td><td class="rblock">   <span class="insert">"HTTP Status Codes"</span> registry is maintained at</td><td class="lineno" valign="top"></td></tr>
    828786      <tr><td class="lineno" valign="top"></td><td class="left">   &lt;http://www.iana.org/assignments/http-status-codes&gt;.</td><td> </td><td class="right">   &lt;http://www.iana.org/assignments/http-status-codes&gt;.</td><td class="lineno" valign="top"></td></tr>
     
    837795      <tr><td class="lineno" valign="top"></td><td class="left">   o  Status Code (3 digits)</td><td> </td><td class="right">   o  Status Code (3 digits)</td><td class="lineno" valign="top"></td></tr>
    838796      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    839       <tr bgcolor="gray" ><td></td><th><a name="part-l26" /><small>skipping to change at</small><em> page 76, line 49</em></th><th> </th><th><a name="part-r26" /><small>skipping to change at</small><em> page 76, line 49</em></th><td></td></tr>
     797      <tr bgcolor="gray" ><td></td><th><a name="part-l25" /><small>skipping to change at</small><em> page 76, line 49</em></th><th> </th><th><a name="part-r25" /><small>skipping to change at</small><em> page 76, line 49</em></th><td></td></tr>
    840798      <tr><td class="lineno" valign="top"></td><td class="left">   cached without explicit freshness information.  Likewise, the</td><td> </td><td class="right">   cached without explicit freshness information.  Likewise, the</td><td class="lineno" valign="top"></td></tr>
    841799      <tr><td class="lineno" valign="top"></td><td class="left">   definition of a status code can place constraints upon cache</td><td> </td><td class="right">   definition of a status code can place constraints upon cache</td><td class="lineno" valign="top"></td></tr>
     
    848806      <tr><td class="lineno" valign="top"></td><td class="left">8.2.3.  Registrations</td><td> </td><td class="right">8.2.3.  Registrations</td><td class="lineno" valign="top"></td></tr>
    849807      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    850       <tr><td><a name="diff0041" /></td></tr>
     808      <tr><td><a name="diff0039" /></td></tr>
    851809      <tr><td class="lineno" valign="top"></td><td class="lblock">   The <span class="delete">status code</span> registry has been updated with the registrations</td><td> </td><td class="rblock">   The <span class="insert">"HTTP Status Codes"</span> registry has been updated with the</td><td class="lineno" valign="top"></td></tr>
    852810      <tr><td class="lineno" valign="top"></td><td class="lblock">   below:</td><td> </td><td class="rblock">   registrations below:</td><td class="lineno" valign="top"></td></tr>
     
    862820      <tr><td class="lineno" valign="top"></td><td class="left">   | 203   | Non-Authoritative Information | Section 6.3.4  |</td><td> </td><td class="right">   | 203   | Non-Authoritative Information | Section 6.3.4  |</td><td class="lineno" valign="top"></td></tr>
    863821      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    864       <tr bgcolor="gray" ><td></td><th><a name="part-l27" /><small>skipping to change at</small><em> page 77, line 49</em></th><th> </th><th><a name="part-r27" /><small>skipping to change at</small><em> page 77, line 49</em></th><td></td></tr>
     822      <tr bgcolor="gray" ><td></td><th><a name="part-l26" /><small>skipping to change at</small><em> page 77, line 49</em></th><th> </th><th><a name="part-r26" /><small>skipping to change at</small><em> page 77, line 49</em></th><td></td></tr>
    865823      <tr><td class="lineno" valign="top"></td><td class="left">   | 501   | Not Implemented               | Section 6.6.2  |</td><td> </td><td class="right">   | 501   | Not Implemented               | Section 6.6.2  |</td><td class="lineno" valign="top"></td></tr>
    866824      <tr><td class="lineno" valign="top"></td><td class="left">   | 502   | Bad Gateway                   | Section 6.6.3  |</td><td> </td><td class="right">   | 502   | Bad Gateway                   | Section 6.6.3  |</td><td class="lineno" valign="top"></td></tr>
     
    873831      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    874832      <tr><td class="lineno" valign="top"></td><td class="left">   HTTP header fields are registered within the "Message Headers"</td><td> </td><td class="right">   HTTP header fields are registered within the "Message Headers"</td><td class="lineno" valign="top"></td></tr>
    875       <tr><td><a name="diff0042" /></td></tr>
     833      <tr><td><a name="diff0040" /></td></tr>
    876834      <tr><td class="lineno" valign="top"></td><td class="lblock">   registry located at</td><td> </td><td class="rblock">   registry located at <span class="insert">&lt;http://www.iana.org/assignments/message-headers&gt;</span></td><td class="lineno" valign="top"></td></tr>
    877835      <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">&lt;http://www.iana.org/assignments/message-headers&gt;,</span> as defined by</td><td> </td><td class="rblock">   as defined by [BCP90].</td><td class="lineno" valign="top"></td></tr>
     
    897855      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    898856      <tr><td class="lineno" valign="top"></td><td class="left">   New header field values typically have their syntax defined using</td><td> </td><td class="right">   New header field values typically have their syntax defined using</td><td class="lineno" valign="top"></td></tr>
    899       <tr><td><a name="diff0043" /></td></tr>
     857      <tr><td><a name="diff0041" /></td></tr>
    900858      <tr><td class="lineno" valign="top"></td><td class="lblock">   ABNF <span class="delete">([RFC5234]), using</span> the extension defined in Section 7 of</td><td> </td><td class="rblock">   ABNF <span class="insert">([RFC5234]) (implementing</span> the extension defined in Section 7 of</td><td class="lineno" valign="top"></td></tr>
    901859      <tr><td class="lineno" valign="top"></td><td class="lblock">   [RFC7230] as <span class="delete">necessary,</span> and are usually constrained to the range of</td><td> </td><td class="rblock">   [RFC7230] as <span class="insert">necessary),</span> and <span class="insert">they</span> are usually constrained to the</td><td class="lineno" valign="top"></td></tr>
     
    912870      <tr><td class="lineno" valign="top"></td><td class="left">   values, they need to be treated with care if they are allowed in the</td><td> </td><td class="right">   values, they need to be treated with care if they are allowed in the</td><td class="lineno" valign="top"></td></tr>
    913871      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    914       <tr bgcolor="gray" ><td></td><th><a name="part-l28" /><small>skipping to change at</small><em> page 80, line 49</em></th><th> </th><th><a name="part-r28" /><small>skipping to change at</small><em> page 80, line 49</em></th><td></td></tr>
     872      <tr bgcolor="gray" ><td></td><th><a name="part-l27" /><small>skipping to change at</small><em> page 80, line 49</em></th><th> </th><th><a name="part-r27" /><small>skipping to change at</small><em> page 80, line 49</em></th><td></td></tr>
    915873      <tr><td class="lineno" valign="top"></td><td class="left">   | User-Agent        | http     | standard | Section 5.5.3   |</td><td> </td><td class="right">   | User-Agent        | http     | standard | Section 5.5.3   |</td><td class="lineno" valign="top"></td></tr>
    916874      <tr><td class="lineno" valign="top"></td><td class="left">   | Vary              | http     | standard | Section 7.1.4   |</td><td> </td><td class="right">   | Vary              | http     | standard | Section 7.1.4   |</td><td class="lineno" valign="top"></td></tr>
     
    923881      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    924882      <tr><td class="lineno" valign="top"></td><td class="left">   The "HTTP Content Coding Registry" defines the namespace for content</td><td> </td><td class="right">   The "HTTP Content Coding Registry" defines the namespace for content</td><td class="lineno" valign="top"></td></tr>
    925       <tr><td><a name="diff0044" /></td></tr>
     883      <tr><td><a name="diff0042" /></td></tr>
    926884      <tr><td class="lineno" valign="top"></td><td class="lblock">   coding names (Section 4.2 of [RFC7230]).  The <span class="delete">content coding registry</span></td><td> </td><td class="rblock">   coding names (Section 4.2 of [RFC7230]).  The <span class="insert">"HTTP Content Coding</span></td><td class="lineno" valign="top"></td></tr>
    927885      <tr><td class="lineno" valign="top"></td><td class="lblock">   is maintained at &lt;http://www.iana.org/assignments/http-parameters&gt;.</td><td> </td><td class="rblock"><span class="insert">   Registry"</span> is maintained at</td><td class="lineno" valign="top"></td></tr>
     
    930888      <tr><td class="lineno" valign="top"></td><td class="left">8.4.1.  Procedure</td><td> </td><td class="right">8.4.1.  Procedure</td><td class="lineno" valign="top"></td></tr>
    931889      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    932       <tr><td><a name="diff0045" /></td></tr>
    933       <tr><td class="lineno" valign="top"></td><td class="lblock">   Content <span class="delete">C</span>oding registrations MUST include the following fields:</td><td> </td><td class="rblock">   Content <span class="insert">c</span>oding registrations MUST include the following fields:</td><td class="lineno" valign="top"></td></tr>
     890      <tr><td class="lineno" valign="top"></td><td class="left">   Content coding registrations MUST include the following fields:</td><td> </td><td class="right">   Content coding registrations MUST include the following fields:</td><td class="lineno" valign="top"></td></tr>
    934891      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    935892      <tr><td class="lineno" valign="top"></td><td class="left">   o  Name</td><td> </td><td class="right">   o  Name</td><td class="lineno" valign="top"></td></tr>
     
    938895      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    939896      <tr><td class="lineno" valign="top"></td><td class="left">   o  Pointer to specification text</td><td> </td><td class="right">   o  Pointer to specification text</td><td class="lineno" valign="top"></td></tr>
    940       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    941       <tr><td class="lineno" valign="top"></td><td class="left">   Names of content codings MUST NOT overlap with names of transfer</td><td> </td><td class="right">   Names of content codings MUST NOT overlap with names of transfer</td><td class="lineno" valign="top"></td></tr>
     897      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
     898      <tr bgcolor="gray" ><td></td><th><a name="part-l28" /><small>skipping to change at</small><em> page 81, line 26</em></th><th> </th><th><a name="part-r28" /><small>skipping to change at</small><em> page 81, line 26</em></th><td></td></tr>
    942899      <tr><td class="lineno" valign="top"></td><td class="left">   codings (Section 4 of [RFC7230]), unless the encoding transformation</td><td> </td><td class="right">   codings (Section 4 of [RFC7230]), unless the encoding transformation</td><td class="lineno" valign="top"></td></tr>
    943900      <tr><td class="lineno" valign="top"></td><td class="left">   is identical (as is the case for the compression codings defined in</td><td> </td><td class="right">   is identical (as is the case for the compression codings defined in</td><td class="lineno" valign="top"></td></tr>
     
    945902      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    946903      <tr><td class="lineno" valign="top"></td><td class="left">   Values to be added to this namespace require IETF Review (see Section</td><td> </td><td class="right">   Values to be added to this namespace require IETF Review (see Section</td><td class="lineno" valign="top"></td></tr>
    947       <tr><td><a name="diff0046" /></td></tr>
    948       <tr><td class="lineno" valign="top"></td><td class="lblock">   4.1 of [RFC5226])<span class="delete">,</span> and MUST conform to the purpose of content coding</td><td> </td><td class="rblock">   4.1 of [RFC5226]) and MUST conform to the purpose of content coding</td><td class="lineno" valign="top"></td></tr>
     904      <tr><td class="lineno" valign="top"></td><td class="left">   4.1 of [RFC5226]) and MUST conform to the purpose of content coding</td><td> </td><td class="right">   4.1 of [RFC5226]) and MUST conform to the purpose of content coding</td><td class="lineno" valign="top"></td></tr>
    949905      <tr><td class="lineno" valign="top"></td><td class="left">   defined in this section.</td><td> </td><td class="right">   defined in this section.</td><td class="lineno" valign="top"></td></tr>
    950906      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    951907      <tr><td class="lineno" valign="top"></td><td class="left">8.4.2.  Registrations</td><td> </td><td class="right">8.4.2.  Registrations</td><td class="lineno" valign="top"></td></tr>
    952908      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    953       <tr><td><a name="diff0047" /></td></tr>
     909      <tr><td><a name="diff0043" /></td></tr>
    954910      <tr><td class="lineno" valign="top"></td><td class="lblock">   The "HTTP Content Coding Registry" has been updated with the</td><td> </td><td class="rblock">   The "HTTP Content Coding<span class="insert">s</span> Registry" has been updated with the</td><td class="lineno" valign="top"></td></tr>
    955911      <tr><td class="lineno" valign="top"></td><td class="left">   registrations below:</td><td> </td><td class="right">   registrations below:</td><td class="lineno" valign="top"></td></tr>
     
    972928      <tr><td class="lineno" valign="top"></td><td class="left">   The list of considerations below is not exhaustive.  Most security</td><td> </td><td class="right">   The list of considerations below is not exhaustive.  Most security</td><td class="lineno" valign="top"></td></tr>
    973929      <tr><td class="lineno" valign="top"></td><td class="left">   concerns related to HTTP semantics are about securing server-side</td><td> </td><td class="right">   concerns related to HTTP semantics are about securing server-side</td><td class="lineno" valign="top"></td></tr>
    974       <tr><td><a name="diff0048" /></td></tr>
     930      <tr><td><a name="diff0044" /></td></tr>
    975931      <tr><td class="lineno" valign="top"></td><td class="lblock">   applications (code behind the HTTP <span class="delete">interface),</span> securing <span class="delete">user agent</span></td><td> </td><td class="rblock">   applications (code behind the HTTP <span class="insert">interface) or</span> securing <span class="insert">user-agent</span></td><td class="lineno" valign="top"></td></tr>
    976932      <tr><td class="lineno" valign="top"></td><td class="lblock">   processing of payloads received via <span class="delete">HTTP, or secure</span> use of the</td><td> </td><td class="rblock">   processing of payloads received via <span class="insert">HTTP.  Secure</span> use of the Internet</td><td class="lineno" valign="top"></td></tr>
     
    1001957      <tr><td class="lineno" valign="top"></td><td class="left">   case-insensitive names.</td><td> </td><td class="right">   case-insensitive names.</td><td class="lineno" valign="top"></td></tr>
    1002958      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1003       <tr><td><a name="diff0049" /></td></tr>
     959      <tr><td><a name="diff0045" /></td></tr>
    1004960      <tr><td class="lineno" valign="top"></td><td class="lblock">   Attacks based on such special names tend to focus on either <span class="delete">denial-</span></td><td> </td><td class="rblock">   Attacks based on such special names tend to focus on either <span class="insert">denial of</span></td><td class="lineno" valign="top"></td></tr>
    1005961      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   of-service</span> (e.g., telling the server to read from a COM port) or</td><td> </td><td class="rblock"><span class="insert">   service</span> (e.g., telling the server to read from a COM port) or</td><td class="lineno" valign="top"></td></tr>
     
    1026982      <tr><td class="lineno" valign="top"></td><td class="left">   [RFC7230]  Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer</td><td> </td><td class="right">   [RFC7230]  Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer</td><td class="lineno" valign="top"></td></tr>
    1027983      <tr><td class="lineno" valign="top"></td><td class="left">              Protocol (HTTP/1.1): Message Syntax and Routing",</td><td> </td><td class="right">              Protocol (HTTP/1.1): Message Syntax and Routing",</td><td class="lineno" valign="top"></td></tr>
    1028       <tr><td><a name="diff0050" /></td></tr>
     984      <tr><td><a name="diff0046" /></td></tr>
    1029985      <tr><td class="lineno" valign="top"></td><td class="lblock">              <span class="delete">draft-ietf-httpbis-p1-messaging-latest (work in progress),</span></td><td> </td><td class="rblock">              <span class="insert">RFC 7230,</span> May 2014.</td><td class="lineno" valign="top"></td></tr>
    1030986      <tr><td class="lineno" valign="top"></td><td class="lblock">              May 2014.</td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    1031987      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1032988      <tr><td class="lineno" valign="top"></td><td class="left">   [RFC7232]  Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer</td><td> </td><td class="right">   [RFC7232]  Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer</td><td class="lineno" valign="top"></td></tr>
    1033       <tr><td><a name="diff0051" /></td></tr>
     989      <tr><td><a name="diff0047" /></td></tr>
    1034990      <tr><td class="lineno" valign="top"></td><td class="lblock">              Protocol (HTTP/1.1): Conditional Requests",</td><td> </td><td class="rblock">              Protocol (HTTP/1.1): Conditional Requests", <span class="insert">RFC 7232,</span></td><td class="lineno" valign="top"></td></tr>
    1035991      <tr><td class="lineno" valign="top"></td><td class="lblock">              <span class="delete">draft-ietf-httpbis-p4-conditional-latest (work in</span></td><td> </td><td class="rblock">              May 2014.</td><td class="lineno" valign="top"></td></tr>
     
    1038994      <tr><td class="lineno" valign="top"></td><td class="left">   [RFC7233]  Fielding, R., Ed., Lafon, Y., Ed., and J. Reschke, Ed.,</td><td> </td><td class="right">   [RFC7233]  Fielding, R., Ed., Lafon, Y., Ed., and J. Reschke, Ed.,</td><td class="lineno" valign="top"></td></tr>
    1039995      <tr><td class="lineno" valign="top"></td><td class="left">              "Hypertext Transfer Protocol (HTTP/1.1): Range Requests",</td><td> </td><td class="right">              "Hypertext Transfer Protocol (HTTP/1.1): Range Requests",</td><td class="lineno" valign="top"></td></tr>
    1040       <tr><td><a name="diff0052" /></td></tr>
     996      <tr><td><a name="diff0048" /></td></tr>
    1041997      <tr><td class="lineno" valign="top"></td><td class="lblock">              <span class="delete">draft-ietf-httpbis-p5-range-latest (work in progress),</span></td><td> </td><td class="rblock">              <span class="insert">RFC 7233,</span> May 2014.</td><td class="lineno" valign="top"></td></tr>
    1042998      <tr><td class="lineno" valign="top"></td><td class="lblock">              May 2014.</td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     
    10441000      <tr><td class="lineno" valign="top"></td><td class="left">   [RFC7234]  Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke,</td><td> </td><td class="right">   [RFC7234]  Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke,</td><td class="lineno" valign="top"></td></tr>
    10451001      <tr><td class="lineno" valign="top"></td><td class="left">              Ed., "Hypertext Transfer Protocol (HTTP/1.1): Caching",</td><td> </td><td class="right">              Ed., "Hypertext Transfer Protocol (HTTP/1.1): Caching",</td><td class="lineno" valign="top"></td></tr>
    1046       <tr><td><a name="diff0053" /></td></tr>
     1002      <tr><td><a name="diff0049" /></td></tr>
    10471003      <tr><td class="lineno" valign="top"></td><td class="lblock">              <span class="delete">draft-ietf-httpbis-p6-cache-latest (work in progress),</span></td><td> </td><td class="rblock">              <span class="insert">RFC 7234,</span> May 2014.</td><td class="lineno" valign="top"></td></tr>
    10481004      <tr><td class="lineno" valign="top"></td><td class="lblock">              May 2014.</td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    10491005      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    10501006      <tr><td class="lineno" valign="top"></td><td class="left">   [RFC7235]  Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer</td><td> </td><td class="right">   [RFC7235]  Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer</td><td class="lineno" valign="top"></td></tr>
    1051       <tr><td><a name="diff0054" /></td></tr>
     1007      <tr><td><a name="diff0050" /></td></tr>
    10521008      <tr><td class="lineno" valign="top"></td><td class="lblock">              Protocol (HTTP/1.1): Authentication",</td><td> </td><td class="rblock">              Protocol (HTTP/1.1): Authentication", <span class="insert">RFC 7235,</span> May 2014.</td><td class="lineno" valign="top"></td></tr>
    10531009      <tr><td class="lineno" valign="top"></td><td class="lblock">              <span class="delete">draft-ietf-httpbis-p7-auth-latest (work in progress),</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     
    10751031      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    10761032      <tr><td class="lineno" valign="top"></td><td class="left">   [RFC7238]  Reschke, J., "The Hypertext Transfer Protocol (HTTP)</td><td> </td><td class="right">   [RFC7238]  Reschke, J., "The Hypertext Transfer Protocol (HTTP)</td><td class="lineno" valign="top"></td></tr>
    1077       <tr><td><a name="diff0055" /></td></tr>
     1033      <tr><td><a name="diff0051" /></td></tr>
    10781034      <tr><td class="lineno" valign="top"></td><td class="lblock">              Status Code 308 (Permanent Redirect)",</td><td> </td><td class="rblock">              Status Code 308 (Permanent Redirect)", <span class="insert">RFC 7238, May 2014.</span></td><td class="lineno" valign="top"></td></tr>
    10791035      <tr><td class="lineno" valign="top"></td><td class="lblock">              <span class="delete">draft-reschke-http-status-308-07 (work in progress),</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     
    11011057      <tr><td class="lineno" valign="top"></td><td class="left">   likelihood of safe transport over the destination protocol.</td><td> </td><td class="right">   likelihood of safe transport over the destination protocol.</td><td class="lineno" valign="top"></td></tr>
    11021058      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1103       <tr><td><a name="diff0056" /></td></tr>
     1059      <tr><td><a name="diff0052" /></td></tr>
    11041060      <tr><td class="lineno" valign="top"></td><td class="lblock">A.6.  MHTML and Line<span class="delete"> </span>Length Limitations</td><td> </td><td class="rblock">A.6.  MHTML and Line<span class="insert">-</span>Length Limitations</td><td class="lineno" valign="top"></td></tr>
    11051061      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    11061062      <tr><td class="lineno" valign="top"></td><td class="left">   HTTP implementations that share code with MHTML [RFC2557]</td><td> </td><td class="right">   HTTP implementations that share code with MHTML [RFC2557]</td><td class="lineno" valign="top"></td></tr>
    1107       <tr><td><a name="diff0057" /></td></tr>
     1063      <tr><td><a name="diff0053" /></td></tr>
    11081064      <tr><td class="lineno" valign="top"></td><td class="lblock">   implementations need to be aware of MIME line<span class="delete"> </span>length limitations.</td><td> </td><td class="rblock">   implementations need to be aware of MIME line<span class="insert">-</span>length limitations.</td><td class="lineno" valign="top"></td></tr>
    11091065      <tr><td class="lineno" valign="top"></td><td class="left">   Since HTTP does not have this limitation, HTTP does not fold long</td><td> </td><td class="right">   Since HTTP does not have this limitation, HTTP does not fold long</td><td class="lineno" valign="top"></td></tr>
    11101066      <tr><td class="lineno" valign="top"></td><td class="left">   lines.  MHTML messages being transported by HTTP follow all</td><td> </td><td class="right">   lines.  MHTML messages being transported by HTTP follow all</td><td class="lineno" valign="top"></td></tr>
    1111       <tr><td><a name="diff0058" /></td></tr>
     1067      <tr><td><a name="diff0054" /></td></tr>
    11121068      <tr><td class="lineno" valign="top"></td><td class="lblock">   conventions of MHTML, including line<span class="delete"> </span>length limitations and folding,</td><td> </td><td class="rblock">   conventions of MHTML, including line<span class="insert">-</span>length limitations and folding,</td><td class="lineno" valign="top"></td></tr>
    11131069      <tr><td class="lineno" valign="top"></td><td class="left">   canonicalization, etc., since HTTP transfers message-bodies as</td><td> </td><td class="right">   canonicalization, etc., since HTTP transfers message-bodies as</td><td class="lineno" valign="top"></td></tr>
     
    11281084      <tr><td class="lineno" valign="top"></td><td class="left">   A new requirement has been added that semantics embedded in a URI be</td><td> </td><td class="right">   A new requirement has been added that semantics embedded in a URI be</td><td class="lineno" valign="top"></td></tr>
    11291085      <tr><td class="lineno" valign="top"></td><td class="left">   disabled when those semantics are inconsistent with the request</td><td> </td><td class="right">   disabled when those semantics are inconsistent with the request</td><td class="lineno" valign="top"></td></tr>
    1130       <tr><td><a name="diff0059" /></td></tr>
     1086      <tr><td><a name="diff0055" /></td></tr>
    11311087      <tr><td class="lineno" valign="top"></td><td class="lblock">   method, since this is a common cause of interoperability <span class="delete">failure.</span></td><td> </td><td class="rblock">   method, since this is a common cause of interoperability <span class="insert">failure</span></td><td class="lineno" valign="top"></td></tr>
    11321088      <tr><td class="lineno" valign="top"></td><td class="lblock">                                                                         </td><td> </td><td class="rblock">   (Section <span class="insert">2).</span></td><td class="lineno" valign="top"></td></tr>
     
    11341090      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    11351091      <tr><td class="lineno" valign="top"></td><td class="left">   An algorithm has been added for determining if a payload is</td><td> </td><td class="right">   An algorithm has been added for determining if a payload is</td><td class="lineno" valign="top"></td></tr>
    1136       <tr><td><a name="diff0060" /></td></tr>
     1092      <tr><td><a name="diff0056" /></td></tr>
    11371093      <tr><td class="lineno" valign="top"></td><td class="lblock">   associated with a specific identifier<span class="delete">.  (Section 3.1.4.1)</span></td><td> </td><td class="rblock">   associated with a specific identifier<span class="insert"> (Section 3.1.4.1).</span></td><td class="lineno" valign="top"></td></tr>
    11381094      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     
    11401096      <tr><td class="lineno" valign="top"></td><td class="left">   removed; the default is now whatever the media type definition says.</td><td> </td><td class="right">   removed; the default is now whatever the media type definition says.</td><td class="lineno" valign="top"></td></tr>
    11411097      <tr><td class="lineno" valign="top"></td><td class="left">   Likewise, special treatment of ISO-8859-1 has been removed from the</td><td> </td><td class="right">   Likewise, special treatment of ISO-8859-1 has been removed from the</td><td class="lineno" valign="top"></td></tr>
    1142       <tr><td><a name="diff0061" /></td></tr>
     1098      <tr><td><a name="diff0057" /></td></tr>
    11431099      <tr><td class="lineno" valign="top"></td><td class="lblock">   Accept-Charset header field.  (Section<span class="delete"> 3.1.1.3 and Section 5.3.3</span>)</td><td> </td><td class="rblock">   Accept-Charset header field.  (Section<span class="insert">s 3.1.1.3 and 5.3.3.</span>)</td><td class="lineno" valign="top"></td></tr>
    11441100      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     
    11461102      <tr><td class="lineno" valign="top"></td><td class="left">   affect the base URI for resolving relative URI references, due to</td><td> </td><td class="right">   affect the base URI for resolving relative URI references, due to</td><td class="lineno" valign="top"></td></tr>
    11471103      <tr><td class="lineno" valign="top"></td><td class="left">   poor implementation support and the undesirable effect of potentially</td><td> </td><td class="right">   poor implementation support and the undesirable effect of potentially</td><td class="lineno" valign="top"></td></tr>
    1148       <tr><td><a name="diff0062" /></td></tr>
     1104      <tr><td><a name="diff0058" /></td></tr>
    11491105      <tr><td class="lineno" valign="top"></td><td class="lblock">   breaking relative links in content-negotiated <span class="delete">resources.</span></td><td> </td><td class="rblock">   breaking relative links in content-negotiated <span class="insert">resources</span></td><td class="lineno" valign="top"></td></tr>
    11501106      <tr><td class="lineno" valign="top"></td><td class="lblock">   (Section <span class="delete">3.1.4.2)</span></td><td> </td><td class="rblock">   (Section <span class="insert">3.1.4.2).</span></td><td class="lineno" valign="top"></td></tr>
     
    11521108      <tr><td class="lineno" valign="top"></td><td class="left">   To be consistent with the method-neutral parsing algorithm of</td><td> </td><td class="right">   To be consistent with the method-neutral parsing algorithm of</td><td class="lineno" valign="top"></td></tr>
    11531109      <tr><td class="lineno" valign="top"></td><td class="left">   [RFC7230], the definition of GET has been relaxed so that requests</td><td> </td><td class="right">   [RFC7230], the definition of GET has been relaxed so that requests</td><td class="lineno" valign="top"></td></tr>
    1154       <tr><td><a name="diff0063" /></td></tr>
     1110      <tr><td><a name="diff0059" /></td></tr>
    11551111      <tr><td class="lineno" valign="top"></td><td class="lblock">   can have a body, even though a body has no meaning for <span class="delete">GET.</span></td><td> </td><td class="rblock">   can have a body, even though a body has no meaning for <span class="insert">GET</span></td><td class="lineno" valign="top"></td></tr>
    11561112      <tr><td class="lineno" valign="top"></td><td class="lblock">   (Section <span class="delete">4.3.1)</span></td><td> </td><td class="rblock">   (Section <span class="insert">4.3.1).</span></td><td class="lineno" valign="top"></td></tr>
    11571113      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    11581114      <tr><td class="lineno" valign="top"></td><td class="left">   Servers are no longer required to handle all Content-* header fields</td><td> </td><td class="right">   Servers are no longer required to handle all Content-* header fields</td><td class="lineno" valign="top"></td></tr>
    1159       <tr><td><a name="diff0064" /></td></tr>
     1115      <tr><td><a name="diff0060" /></td></tr>
    11601116      <tr><td class="lineno" valign="top"></td><td class="lblock">   and use of Content-Range has been explicitly banned in PUT <span class="delete">requests.</span></td><td> </td><td class="rblock">   and use of Content-Range has been explicitly banned in PUT <span class="insert">requests</span></td><td class="lineno" valign="top"></td></tr>
    11611117      <tr><td class="lineno" valign="top"></td><td class="lblock">   (Section <span class="delete">4.3.4)</span></td><td> </td><td class="rblock">   (Section <span class="insert">4.3.4).</span></td><td class="lineno" valign="top"></td></tr>
    11621118      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    11631119      <tr><td class="lineno" valign="top"></td><td class="left">   Definition of the CONNECT method has been moved from [RFC2817] to</td><td> </td><td class="right">   Definition of the CONNECT method has been moved from [RFC2817] to</td><td class="lineno" valign="top"></td></tr>
    1164       <tr><td><a name="diff0065" /></td></tr>
     1120      <tr><td><a name="diff0061" /></td></tr>
    11651121      <tr><td class="lineno" valign="top"></td><td class="lblock">   this specification<span class="delete">.  (Section 4.3.6)</span></td><td> </td><td class="rblock">   this specification<span class="insert"> (Section 4.3.6).</span></td><td class="lineno" valign="top"></td></tr>
    11661122      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1167       <tr><td><a name="diff0066" /></td></tr>
     1123      <tr><td><a name="diff0062" /></td></tr>
    11681124      <tr><td class="lineno" valign="top"></td><td class="lblock">   The OPTIONS and TRACE request methods have been defined as being</td><td> </td><td class="rblock">   The OPTIONS and TRACE request methods have been defined as being <span class="insert">safe</span></td><td class="lineno" valign="top"></td></tr>
    11691125      <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">safe.</span>  (Section 4.3.7 and Section <span class="delete">4.3.8)</span></td><td> </td><td class="rblock">   (Section 4.3.7 and Section <span class="insert">4.3.8).</span></td><td class="lineno" valign="top"></td></tr>
    11701126      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    11711127      <tr><td class="lineno" valign="top"></td><td class="left">   The Expect header field's extension mechanism has been removed due to</td><td> </td><td class="right">   The Expect header field's extension mechanism has been removed due to</td><td class="lineno" valign="top"></td></tr>
    1172       <tr><td><a name="diff0067" /></td></tr>
     1128      <tr><td><a name="diff0063" /></td></tr>
    11731129      <tr><td class="lineno" valign="top"></td><td class="lblock">   widely<span class="delete">-deployed broken implementations.  (Section 5.1.1)</span></td><td> </td><td class="rblock">   widely<span class="insert"> deployed broken implementations (Section 5.1.1).</span></td><td class="lineno" valign="top"></td></tr>
    11741130      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    11751131      <tr><td class="lineno" valign="top"></td><td class="left">   The Max-Forwards header field has been restricted to the OPTIONS and</td><td> </td><td class="right">   The Max-Forwards header field has been restricted to the OPTIONS and</td><td class="lineno" valign="top"></td></tr>
    11761132      <tr><td class="lineno" valign="top"></td><td class="left">   TRACE methods; previously, extension methods could have used it as</td><td> </td><td class="right">   TRACE methods; previously, extension methods could have used it as</td><td class="lineno" valign="top"></td></tr>
    1177       <tr><td><a name="diff0068" /></td></tr>
     1133      <tr><td><a name="diff0064" /></td></tr>
    11781134      <tr><td class="lineno" valign="top"></td><td class="lblock">   well<span class="delete">.  (Section 5.1.2)</span></td><td> </td><td class="rblock">   well<span class="insert"> (Section 5.1.2).</span></td><td class="lineno" valign="top"></td></tr>
    11791135      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     
    11811137      <tr><td class="lineno" valign="top"></td><td class="left">   header field when no referring URI is applicable, which distinguishes</td><td> </td><td class="right">   header field when no referring URI is applicable, which distinguishes</td><td class="lineno" valign="top"></td></tr>
    11821138      <tr><td class="lineno" valign="top"></td><td class="left">   that case from others where the Referer field is not sent or has been</td><td> </td><td class="right">   that case from others where the Referer field is not sent or has been</td><td class="lineno" valign="top"></td></tr>
    1183       <tr><td><a name="diff0069" /></td></tr>
     1139      <tr><td><a name="diff0065" /></td></tr>
    11841140      <tr><td class="lineno" valign="top"></td><td class="lblock">   removed<span class="delete">.  (Section 5.5.2)</span></td><td> </td><td class="rblock">   removed<span class="insert"> (Section 5.5.2).</span></td><td class="lineno" valign="top"></td></tr>
    11851141      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    11861142      <tr><td class="lineno" valign="top"></td><td class="left">   The following status codes are now cacheable (that is, they can be</td><td> </td><td class="right">   The following status codes are now cacheable (that is, they can be</td><td class="lineno" valign="top"></td></tr>
    11871143      <tr><td class="lineno" valign="top"></td><td class="left">   stored and reused by a cache without explicit freshness information</td><td> </td><td class="right">   stored and reused by a cache without explicit freshness information</td><td class="lineno" valign="top"></td></tr>
    1188       <tr><td><a name="diff0070" /></td></tr>
     1144      <tr><td><a name="diff0066" /></td></tr>
    11891145      <tr><td class="lineno" valign="top"></td><td class="lblock">   present): 204, 404, 405, 414, 501<span class="delete">.  (Section 6)</span></td><td> </td><td class="rblock">   present): 204, 404, 405, 414, 501<span class="insert"> (Section 6).</span></td><td class="lineno" valign="top"></td></tr>
    11901146      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    11911147      <tr><td class="lineno" valign="top"></td><td class="left">   The 201 (Created) status description has been changed to allow for</td><td> </td><td class="right">   The 201 (Created) status description has been changed to allow for</td><td class="lineno" valign="top"></td></tr>
    1192       <tr><td><a name="diff0071" /></td></tr>
     1148      <tr><td><a name="diff0067" /></td></tr>
    11931149      <tr><td class="lineno" valign="top"></td><td class="lblock">   the possibility that more than one resource has been <span class="delete">created.</span></td><td> </td><td class="rblock">   the possibility that more than one resource has been <span class="insert">created</span></td><td class="lineno" valign="top"></td></tr>
    11941150      <tr><td class="lineno" valign="top"></td><td class="lblock">   (Section <span class="delete">6.3.2)</span></td><td> </td><td class="rblock">   (Section <span class="insert">6.3.2).</span></td><td class="lineno" valign="top"></td></tr>
    11951151      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    11961152      <tr><td class="lineno" valign="top"></td><td class="left">   The definition of 203 (Non-Authoritative Information) has been</td><td> </td><td class="right">   The definition of 203 (Non-Authoritative Information) has been</td><td class="lineno" valign="top"></td></tr>
    1197       <tr><td><a name="diff0072" /></td></tr>
     1153      <tr><td><a name="diff0068" /></td></tr>
    11981154      <tr><td class="lineno" valign="top"></td><td class="lblock">   broadened to include cases of payload transformations as <span class="delete">well.</span></td><td> </td><td class="rblock">   broadened to include cases of payload transformations as <span class="insert">well</span></td><td class="lineno" valign="top"></td></tr>
    11991155      <tr><td class="lineno" valign="top"></td><td class="lblock">   (Section <span class="delete">6.3.4)</span></td><td> </td><td class="rblock">   (Section <span class="insert">6.3.4).</span></td><td class="lineno" valign="top"></td></tr>
     
    12031159      <tr><td class="lineno" valign="top"></td><td class="left">   based upon the request method semantics.  The redirect status codes</td><td> </td><td class="right">   based upon the request method semantics.  The redirect status codes</td><td class="lineno" valign="top"></td></tr>
    12041160      <tr><td class="lineno" valign="top"></td><td class="left">   301, 302, and 307 no longer have normative requirements on response</td><td> </td><td class="right">   301, 302, and 307 no longer have normative requirements on response</td><td class="lineno" valign="top"></td></tr>
     1161      <tr><td><a name="diff0069" /></td></tr>
     1162      <tr><td class="lineno" valign="top"></td><td class="lblock">   payloads and user interaction<span class="delete">.  (Section 6.4)</span></td><td> </td><td class="rblock">   payloads and user interaction<span class="insert"> (Section 6.4).</span></td><td class="lineno" valign="top"></td></tr>
     1163      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     1164      <tr><td class="lineno" valign="top"></td><td class="left">   The status codes 301 and 302 have been changed to allow user agents</td><td> </td><td class="right">   The status codes 301 and 302 have been changed to allow user agents</td><td class="lineno" valign="top"></td></tr>
     1165      <tr><td><a name="diff0070" /></td></tr>
     1166      <tr><td class="lineno" valign="top"></td><td class="lblock">   to rewrite the method from POST to GET.  (Sections 6.4.2 and 6.4.3)</td><td> </td><td class="rblock">   to rewrite the method from POST to GET.  (Sections 6.4.2 and 6.4.3<span class="insert">.</span>)</td><td class="lineno" valign="top"></td></tr>
     1167      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     1168      <tr><td class="lineno" valign="top"></td><td class="left">   The description of the 303 (See Other) status code has been changed</td><td> </td><td class="right">   The description of the 303 (See Other) status code has been changed</td><td class="lineno" valign="top"></td></tr>
     1169      <tr><td class="lineno" valign="top"></td><td class="left">   to allow it to be cached if explicit freshness information is given,</td><td> </td><td class="right">   to allow it to be cached if explicit freshness information is given,</td><td class="lineno" valign="top"></td></tr>
     1170      <tr><td><a name="diff0071" /></td></tr>
     1171      <tr><td class="lineno" valign="top"></td><td class="lblock">   and a specific definition has been added for a 303 response to <span class="delete">GET.</span></td><td> </td><td class="rblock">   and a specific definition has been added for a 303 response to <span class="insert">GET</span></td><td class="lineno" valign="top"></td></tr>
     1172      <tr><td class="lineno" valign="top"></td><td class="lblock">   (Section <span class="delete">6.4.4)</span></td><td> </td><td class="rblock">   (Section <span class="insert">6.4.4).</span></td><td class="lineno" valign="top"></td></tr>
     1173      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     1174      <tr><td class="lineno" valign="top"></td><td class="left">   The 305 (Use Proxy) status code has been deprecated due to security</td><td> </td><td class="right">   The 305 (Use Proxy) status code has been deprecated due to security</td><td class="lineno" valign="top"></td></tr>
     1175      <tr><td><a name="diff0072" /></td></tr>
     1176      <tr><td class="lineno" valign="top"></td><td class="lblock">   concerns regarding in-band configuration of a proxy<span class="delete">.  (Section 6.4.5)</span></td><td> </td><td class="rblock">   concerns regarding in-band configuration of a proxy<span class="insert"> (Section 6.4.5).</span></td><td class="lineno" valign="top"></td></tr>
     1177      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     1178      <tr><td class="lineno" valign="top"></td><td class="left">   The 400 (Bad Request) status code has been relaxed so that it isn't</td><td> </td><td class="right">   The 400 (Bad Request) status code has been relaxed so that it isn't</td><td class="lineno" valign="top"></td></tr>
    12051179      <tr><td><a name="diff0073" /></td></tr>
    1206       <tr><td class="lineno" valign="top"></td><td class="lblock">   payloads and user interaction<span class="delete">.  (Section 6.4)</span></td><td> </td><td class="rblock">   payloads and user interaction<span class="insert"> (Section 6.4).</span></td><td class="lineno" valign="top"></td></tr>
    1207       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1208       <tr><td class="lineno" valign="top"></td><td class="left">   The status codes 301 and 302 have been changed to allow user agents</td><td> </td><td class="right">   The status codes 301 and 302 have been changed to allow user agents</td><td class="lineno" valign="top"></td></tr>
     1180      <tr><td class="lineno" valign="top"></td><td class="lblock">   limited to syntax errors<span class="delete">.  (Section 6.5.1)</span></td><td> </td><td class="rblock">   limited to syntax errors<span class="insert"> (Section 6.5.1).</span></td><td class="lineno" valign="top"></td></tr>
     1181      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     1182      <tr><td class="lineno" valign="top"></td><td class="left">   The 426 (Upgrade Required) status code has been incorporated from</td><td> </td><td class="right">   The 426 (Upgrade Required) status code has been incorporated from</td><td class="lineno" valign="top"></td></tr>
    12091183      <tr><td><a name="diff0074" /></td></tr>
    1210       <tr><td class="lineno" valign="top"></td><td class="lblock">   to rewrite the method from POST to GET.  (Sections 6.4.2 and 6.4.3)</td><td> </td><td class="rblock">   to rewrite the method from POST to GET.  (Sections 6.4.2 and 6.4.3<span class="insert">.</span>)</td><td class="lineno" valign="top"></td></tr>
    1211       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1212       <tr><td><a name="diff0075" /></td></tr>
    1213       <tr><td class="lineno" valign="top"></td><td class="lblock">   The description of 303 (See Other) status code has been changed to</td><td> </td><td class="rblock">   The description of <span class="insert">the</span> 303 (See Other) status code has been changed</td><td class="lineno" valign="top"></td></tr>
    1214       <tr><td class="lineno" valign="top"></td><td class="lblock">   allow it to be cached if explicit freshness information is given, and</td><td> </td><td class="rblock">   to allow it to be cached if explicit freshness information is given,</td><td class="lineno" valign="top"></td></tr>
    1215       <tr><td class="lineno" valign="top"></td><td class="lblock">   a specific definition has been added for a 303 response to <span class="delete">GET.</span></td><td> </td><td class="rblock">   and a specific definition has been added for a 303 response to <span class="insert">GET</span></td><td class="lineno" valign="top"></td></tr>
    1216       <tr><td class="lineno" valign="top"></td><td class="lblock">   (Section <span class="delete">6.4.4)</span></td><td> </td><td class="rblock">   (Section <span class="insert">6.4.4).</span></td><td class="lineno" valign="top"></td></tr>
    1217       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1218       <tr><td class="lineno" valign="top"></td><td class="left">   The 305 (Use Proxy) status code has been deprecated due to security</td><td> </td><td class="right">   The 305 (Use Proxy) status code has been deprecated due to security</td><td class="lineno" valign="top"></td></tr>
    1219       <tr><td><a name="diff0076" /></td></tr>
    1220       <tr><td class="lineno" valign="top"></td><td class="lblock">   concerns regarding in-band configuration of a proxy<span class="delete">.  (Section 6.4.5)</span></td><td> </td><td class="rblock">   concerns regarding in-band configuration of a proxy<span class="insert"> (Section 6.4.5).</span></td><td class="lineno" valign="top"></td></tr>
    1221       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1222       <tr><td class="lineno" valign="top"></td><td class="left">   The 400 (Bad Request) status code has been relaxed so that it isn't</td><td> </td><td class="right">   The 400 (Bad Request) status code has been relaxed so that it isn't</td><td class="lineno" valign="top"></td></tr>
    1223       <tr><td><a name="diff0077" /></td></tr>
    1224       <tr><td class="lineno" valign="top"></td><td class="lblock">   limited to syntax errors<span class="delete">.  (Section 6.5.1)</span></td><td> </td><td class="rblock">   limited to syntax errors<span class="insert"> (Section 6.5.1).</span></td><td class="lineno" valign="top"></td></tr>
    1225       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1226       <tr><td class="lineno" valign="top"></td><td class="left">   The 426 (Upgrade Required) status code has been incorporated from</td><td> </td><td class="right">   The 426 (Upgrade Required) status code has been incorporated from</td><td class="lineno" valign="top"></td></tr>
    1227       <tr><td><a name="diff0078" /></td></tr>
    12281184      <tr><td class="lineno" valign="top"></td><td class="lblock">   [RFC2817]<span class="delete">.  (Section 6.5.15)</span></td><td> </td><td class="rblock">   [RFC2817]<span class="insert"> (Section 6.5.15).</span></td><td class="lineno" valign="top"></td></tr>
    12291185      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    12301186      <tr><td class="lineno" valign="top"></td><td class="left">   The target of requirements on HTTP-date and the Date header field</td><td> </td><td class="right">   The target of requirements on HTTP-date and the Date header field</td><td class="lineno" valign="top"></td></tr>
    12311187      <tr><td class="lineno" valign="top"></td><td class="left">   have been reduced to those systems generating the date, rather than</td><td> </td><td class="right">   have been reduced to those systems generating the date, rather than</td><td class="lineno" valign="top"></td></tr>
    1232       <tr><td><a name="diff0079" /></td></tr>
     1188      <tr><td><a name="diff0075" /></td></tr>
    12331189      <tr><td class="lineno" valign="top"></td><td class="lblock">   all systems sending a date<span class="delete">.  (Section 7.1.1)</span></td><td> </td><td class="rblock">   all systems sending a date<span class="insert"> (Section 7.1.1).</span></td><td class="lineno" valign="top"></td></tr>
    12341190      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     
    12361192      <tr><td class="lineno" valign="top"></td><td class="left">   URI references, including relative references and fragments, along</td><td> </td><td class="right">   URI references, including relative references and fragments, along</td><td class="lineno" valign="top"></td></tr>
    12371193      <tr><td class="lineno" valign="top"></td><td class="left">   with some clarifications as to when use of fragments would not be</td><td> </td><td class="right">   with some clarifications as to when use of fragments would not be</td><td class="lineno" valign="top"></td></tr>
    1238       <tr><td><a name="diff0080" /></td></tr>
     1194      <tr><td><a name="diff0076" /></td></tr>
    12391195      <tr><td class="lineno" valign="top"></td><td class="lblock">   appropriate<span class="delete">.  (Section 7.1.2)</span></td><td> </td><td class="rblock">   appropriate<span class="insert"> (Section 7.1.2).</span></td><td class="lineno" valign="top"></td></tr>
    12401196      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     
    12421198      <tr><td class="lineno" valign="top"></td><td class="left">   option to specify it in a PUT request.  Requirements relating to the</td><td> </td><td class="right">   option to specify it in a PUT request.  Requirements relating to the</td><td class="lineno" valign="top"></td></tr>
    12431199      <tr><td class="lineno" valign="top"></td><td class="left">   content of Allow have been relaxed; correspondingly, clients are not</td><td> </td><td class="right">   content of Allow have been relaxed; correspondingly, clients are not</td><td class="lineno" valign="top"></td></tr>
    1244       <tr><td><a name="diff0081" /></td></tr>
     1200      <tr><td><a name="diff0077" /></td></tr>
    12451201      <tr><td class="lineno" valign="top"></td><td class="lblock">   required to always trust its value<span class="delete">.  (Section 7.4.1)</span></td><td> </td><td class="rblock">   required to always trust its value<span class="insert"> (Section 7.4.1).</span></td><td class="lineno" valign="top"></td></tr>
    12461202      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1247       <tr><td><a name="diff0082" /></td></tr>
     1203      <tr><td><a name="diff0078" /></td></tr>
    12481204      <tr><td class="lineno" valign="top"></td><td class="lblock">   A Method Registry has been defined<span class="delete">.  (Section 8.1)</span></td><td> </td><td class="rblock">   A Method Registry has been defined<span class="insert"> (Section 8.1).</span></td><td class="lineno" valign="top"></td></tr>
    12491205      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    12501206      <tr><td class="lineno" valign="top"></td><td class="left">   The Status Code Registry has been redefined by this specification;</td><td> </td><td class="right">   The Status Code Registry has been redefined by this specification;</td><td class="lineno" valign="top"></td></tr>
    1251       <tr><td><a name="diff0083" /></td></tr>
     1207      <tr><td><a name="diff0079" /></td></tr>
    12521208      <tr><td class="lineno" valign="top"></td><td class="lblock">   previously, it was defined in Section 7.1 of <span class="delete">[RFC2817].</span></td><td> </td><td class="rblock">   previously, it was defined in Section 7.1 of <span class="insert">[RFC2817]</span> (Section <span class="insert">8.2).</span></td><td class="lineno" valign="top"></td></tr>
    12531209      <tr><td class="lineno" valign="top"></td><td class="lblock">                                                                         </td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    12541210      <tr><td class="lineno" valign="top"></td><td class="lblock">   (Section <span class="delete">8.2)</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    12551211      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1256       <tr><td><a name="diff0084" /></td></tr>
    1257       <tr><td class="lineno" valign="top"></td><td class="lblock">   Registration of <span class="delete">Content Codings</span> has been changed to require IETF</td><td> </td><td class="rblock">   Registration of <span class="insert">content codings</span> has been changed to require IETF</td><td class="lineno" valign="top"></td></tr>
    1258       <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">Review.</span>  (Section <span class="delete">8.4)</span></td><td> </td><td class="rblock">   <span class="insert">Review</span> (Section <span class="insert">8.4).</span></td><td class="lineno" valign="top"></td></tr>
     1212      <tr><td class="lineno" valign="top"></td><td class="left">   Registration of content codings has been changed to require IETF</td><td> </td><td class="right">   Registration of content codings has been changed to require IETF</td><td class="lineno" valign="top"></td></tr>
     1213      <tr><td><a name="diff0080" /></td></tr>
     1214      <tr><td class="lineno" valign="top"></td><td class="lblock">   Review<span class="delete">.  (Section 8.4)</span></td><td> </td><td class="rblock">   Review<span class="insert"> (Section 8.4).</span></td><td class="lineno" valign="top"></td></tr>
    12591215      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    12601216      <tr><td class="lineno" valign="top"></td><td class="left">   The Content-Disposition header field has been removed since it is now</td><td> </td><td class="right">   The Content-Disposition header field has been removed since it is now</td><td class="lineno" valign="top"></td></tr>
     
    12791235      <tr><td class="lineno" valign="top"></td><td class="left">   M</td><td> </td><td class="right">   M</td><td class="lineno" valign="top"></td></tr>
    12801236      <tr><td class="lineno" valign="top"></td><td class="left">      Max-Forwards header field  36</td><td> </td><td class="right">      Max-Forwards header field  36</td><td class="lineno" valign="top"></td></tr>
    1281       <tr><td><a name="diff0085" /></td></tr>
     1237      <tr><td><a name="diff0081" /></td></tr>
    12821238      <tr><td class="lineno" valign="top"></td><td class="lblock">      MIME-Version header field  8<span class="delete">9</span></td><td> </td><td class="rblock">      MIME-Version header field  8<span class="insert">8</span></td><td class="lineno" valign="top"></td></tr>
    12831239      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     
    12931249
    12941250     <tr><td></td><td class="left"></td><td> </td><td class="right"></td><td></td></tr>
    1295      <tr bgcolor="gray"><th colspan="5" align="center"><a name="end">&nbsp;End of changes. 85 change blocks.&nbsp;</a></th></tr>
    1296      <tr class="stats"><td></td><th><i>200 lines changed or deleted</i></th><th><i> </i></th><th><i>172 lines changed or added</i></th><td></td></tr>
     1251     <tr bgcolor="gray"><th colspan="5" align="center"><a name="end">&nbsp;End of changes. 81 change blocks.&nbsp;</a></th></tr>
     1252     <tr class="stats"><td></td><th><i>192 lines changed or deleted</i></th><th><i> </i></th><th><i>164 lines changed or added</i></th><td></td></tr>
    12971253     <tr><td colspan="5" align="center" class="small"><br/>This html diff was produced by rfcdiff 1.38. The latest version is available from <a href="http://www.tools.ietf.org/tools/rfcdiff/" >http://tools.ietf.org/tools/rfcdiff/</a> </td></tr>
    12981254   </table>
  • draft-ietf-httpbis/latest/p2-semantics.html

    r2662 r2663  
     1<!DOCTYPE html
     2  PUBLIC "-//W3C//DTD HTML 4.01//EN">
     3<html lang="en">
     4   <head profile="http://dublincore.org/documents/2008/08/04/dc-html/">
     5      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
     6      <title>Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content</title><script>
     7var buttonsAdded = false;
     8
     9function initFeedback() {
     10  var fb = document.createElement("div");
     11  fb.className = "feedback noprint";
     12  fb.setAttribute("onclick", "feedback();");
     13  fb.appendChild(document.createTextNode("feedback"));
     14
     15  var bodyl = document.getElementsByTagName("body");
     16  bodyl.item(0).appendChild(fb);
     17}
     18
     19function feedback() {
     20  toggleButtonsToElementsByName("h1");
     21  toggleButtonsToElementsByName("h2");
     22  toggleButtonsToElementsByName("h3");
     23  toggleButtonsToElementsByName("h4");
     24
     25  buttonsAdded = !buttonsAdded;
     26}
     27
     28function toggleButtonsToElementsByName(name) {
     29  var list = document.getElementsByTagName(name);
     30  for (var i = 0; i < list.length; i++) {
     31    toggleButton(list.item(i));
     32  }
     33}
     34
     35function toggleButton(node) {
     36  if (! buttonsAdded) {
     37
     38    // docname
     39    var template = "mailto:ietf-http-wg@w3.org?subject={docname},%20%22{section}%22&body=<{ref}>:";
     40
     41    var id = node.getAttribute("id");
     42    // better id available?
     43    var titlelinks = node.getElementsByTagName("a");
     44    for (var i = 0; i < titlelinks.length; i++) {
     45      var tl = titlelinks.item(i);
     46      if (tl.getAttribute("id")) {
     47        id = tl.getAttribute("id");
     48      }
     49    }
     50
     51    // ref
     52    var ref = window.location.toString();
     53    var hash = ref.indexOf("#");
     54    if (hash != -1) {
     55      ref = ref.substring(0, hash);
     56    }
     57    if (id != "") {
     58      ref += "#" + id;
     59    }
     60
     61    // docname
     62    var docname = "draft-ietf-httpbis-p2-semantics-latest";
     63
     64    // section
     65    var section = node.textContent;
     66    section = section.replace("\u00a0", " ");
     67
     68    // build URI from template
     69    var uri = template.replace("{docname}", encodeURIComponent(docname));
     70    uri = uri.replace("{section}", encodeURIComponent(section));
     71    uri = uri.replace("{ref}", encodeURIComponent(ref));
     72
     73    var button = document.createElement("a");
     74    button.className = "fbbutton noprint";
     75    button.setAttribute("href", uri);
     76    button.appendChild(document.createTextNode("send feedback"));
     77    node.appendChild(button);
     78  }
     79  else {
     80    var buttons = node.getElementsByTagName("a");
     81    for (var i = 0; i < buttons.length; i++) {
     82      var b = buttons.item(i);
     83      if (b.className == "fbbutton noprint") {
     84        node.removeChild(b);
     85      }
     86    }
     87  }
     88}</script><style type="text/css" title="Xml2Rfc (sans serif)">
     89a {
     90  text-decoration: none;
     91}
     92a.smpl {
     93  color: black;
     94}
     95a:hover {
     96  text-decoration: underline;
     97}
     98a:active {
     99  text-decoration: underline;
     100}
     101address {
     102  margin-top: 1em;
     103  margin-left: 2em;
     104  font-style: normal;
     105}
     106body {
     107  color: black;
     108  font-family: cambria, helvetica, arial, sans-serif;
     109  font-size: 11pt;
     110  margin-right: 2em;
     111}
     112cite {
     113  font-style: normal;
     114}
     115div.note {
     116  margin-left: 2em;
     117}
     118dl {
     119  margin-left: 2em;
     120}
     121ul.empty {
     122  list-style-type: none;
     123}
     124ul.empty li {
     125  margin-top: .5em;
     126}
     127dl p {
     128  margin-left: 0em;
     129}
     130dt {
     131  margin-top: .5em;
     132}
     133h1 {
     134  font-size: 130%;
     135  line-height: 21pt;
     136  page-break-after: avoid;
     137}
     138h1.np {
     139  page-break-before: always;
     140}
     141h2 {
     142  font-size: 120%;
     143  line-height: 15pt;
     144  page-break-after: avoid;
     145}
     146h3 {
     147  font-size: 110%;
     148  page-break-after: avoid;
     149}
     150h4, h5, h6 {
     151  page-break-after: avoid;
     152}
     153h1 a, h2 a, h3 a, h4 a, h5 a, h6 a {
     154  color: black;
     155}
     156img {
     157  margin-left: 3em;
     158}
     159li {
     160  margin-left: 2em;
     161}
     162ol {
     163  margin-left: 2em;
     164}
     165ol.la {
     166  list-style-type: lower-alpha;
     167}
     168ol.ua {
     169  list-style-type: upper-alpha;
     170}
     171ol p {
     172  margin-left: 0em;
     173}
     174p {
     175  margin-left: 2em;
     176}
     177pre {
     178  margin-left: 3em;
     179  background-color: lightyellow;
     180  padding: .25em;
     181  page-break-inside: avoid;
     182}
     183pre.text2 {
     184  border-style: dotted;
     185  border-width: 1px;
     186  background-color: #f0f0f0;
     187  width: 69em;
     188}
     189pre.inline {
     190  background-color: white;
     191  padding: 0em;
     192}
     193pre.text {
     194  border-style: dotted;
     195  border-width: 1px;
     196  background-color: #f8f8f8;
     197  width: 69em;
     198}
     199pre.drawing {
     200  border-style: solid;
     201  border-width: 1px;
     202  background-color: #f8f8f8;
     203  padding: 2em;
     204}
     205table {
     206  margin-left: 2em;
     207}
     208table.tt {
     209  vertical-align: top;
     210  border-color: gray;
     211}
     212table.tt th {
     213  border-color: gray;
     214}
     215table.tt td {
     216  border-color: gray;
     217}
     218table.all {
     219  border-style: solid;
     220  border-width: 2px;
     221}
     222table.full {
     223  border-style: solid;
     224  border-width: 2px;
     225}
     226table.tt td {
     227  vertical-align: top;
     228}
     229table.all td {
     230  border-style: solid;
     231  border-width: 1px;
     232}
     233table.full td {
     234  border-style: none solid;
     235  border-width: 1px;
     236}
     237table.tt th {
     238  vertical-align: top;
     239}
     240table.all th {
     241  border-style: solid;
     242  border-width: 1px;
     243}
     244table.full th {
     245  border-style: solid;
     246  border-width: 1px 1px 2px 1px;
     247}
     248table.headers th {
     249  border-style: none none solid none;
     250  border-width: 2px;
     251}
     252table.left {
     253  margin-right: auto;
     254}
     255table.right {
     256  margin-left: auto;
     257}
     258table.center {
     259  margin-left: auto;
     260  margin-right: auto;
     261}
     262caption {
     263  caption-side: bottom;
     264  font-weight: bold;
     265  font-size: 10pt;
     266  margin-top: .5em;
     267}
     268
     269table.header {
     270  border-spacing: 1px;
     271  width: 95%;
     272  font-size: 11pt;
     273  color: white;
     274}
     275td.top {
     276  vertical-align: top;
     277}
     278td.topnowrap {
     279  vertical-align: top;
     280  white-space: nowrap;
     281}
     282table.header td {
     283  background-color: gray;
     284  width: 50%;
     285}
     286table.header a {
     287  color: white;
     288}
     289td.reference {
     290  vertical-align: top;
     291  white-space: nowrap;
     292  padding-right: 1em;
     293}
     294thead {
     295  display:table-header-group;
     296}
     297ul.toc, ul.toc ul {
     298  list-style: none;
     299  margin-left: 1.5em;
     300  padding-left: 0em;
     301}
     302ul.toc li {
     303  line-height: 150%;
     304  font-weight: bold;
     305  margin-left: 0em;
     306}
     307ul.toc li li {
     308  line-height: normal;
     309  font-weight: normal;
     310  font-size: 10pt;
     311  margin-left: 0em;
     312}
     313li.excluded {
     314  font-size: 0pt;
     315}
     316ul p {
     317  margin-left: 0em;
     318}
     319.title, .filename, h1, h2, h3, h4 {
     320  font-family: candara, helvetica, arial, sans-serif;
     321}
     322samp, tt, code, pre {
     323  font: consolas, monospace;
     324}
     325ul.ind, ul.ind ul {
     326  list-style: none;
     327  margin-left: 1.5em;
     328  padding-left: 0em;
     329  page-break-before: avoid;
     330}
     331ul.ind li {
     332  font-weight: bold;
     333  line-height: 200%;
     334  margin-left: 0em;
     335}
     336ul.ind li li {
     337  font-weight: normal;
     338  line-height: 150%;
     339  margin-left: 0em;
     340}
     341.avoidbreak {
     342  page-break-inside: avoid;
     343}
     344.bcp14 {
     345  font-style: normal;
     346  text-transform: lowercase;
     347  font-variant: small-caps;
     348}
     349.comment {
     350  background-color: yellow;
     351}
     352.center {
     353  text-align: center;
     354}
     355.error {
     356  color: red;
     357  font-style: italic;
     358  font-weight: bold;
     359}
     360.figure {
     361  font-weight: bold;
     362  text-align: center;
     363  font-size: 10pt;
     364}
     365.filename {
     366  color: #333333;
     367  font-size: 75%;
     368  font-weight: bold;
     369  line-height: 21pt;
     370  text-align: center;
     371}
     372.fn {
     373  font-weight: bold;
     374}
     375.left {
     376  text-align: left;
     377}
     378.right {
     379  text-align: right;
     380}
     381.title {
     382  color: green;
     383  font-size: 150%;
     384  line-height: 18pt;
     385  font-weight: bold;
     386  text-align: center;
     387  margin-top: 36pt;
     388}
     389.warning {
     390  font-size: 130%;
     391  background-color: yellow;
     392}
     393.feedback {
     394  position: fixed;
     395  bottom: 1%;
     396  right: 1%;
     397  padding: 3px 5px;
     398  color: white;
     399  border-radius: 5px;
     400  background: #a00000;
     401  border: 1px solid silver;
     402}
     403.fbbutton {
     404  margin-left: 1em;
     405  color: #303030;
     406  font-size: small;
     407  font-weight: normal;
     408  background: #d0d000;
     409  padding: 1px 4px;
     410  border: 1px solid silver;
     411  border-radius: 5px;
     412}
     413
     414@media print {
     415  .noprint {
     416    display: none;
     417  }
     418
     419  a {
     420    color: black;
     421    text-decoration: none;
     422  }
     423
     424  table.header {
     425    width: 90%;
     426  }
     427
     428  td.header {
     429    width: 50%;
     430    color: black;
     431    background-color: white;
     432    vertical-align: top;
     433    font-size: 110%;
     434  }
     435
     436  ul.toc a:nth-child(2)::after {
     437    content: leader('.') target-counter(attr(href), page);
     438  }
     439
     440  ul.ind li li a {
     441    content: target-counter(attr(href), page);
     442  }
     443
     444  .print2col {
     445    column-count: 2;
     446    -moz-column-count: 2;
     447    column-fill: auto;
     448  }
     449}
     450
     451@page {
     452  @top-left {
     453       content: "Internet-Draft";
     454  }
     455  @top-right {
     456       content: "May 2014";
     457  }
     458  @top-center {
     459       content: "HTTP/1.1 Semantics and Content";
     460  }
     461  @bottom-left {
     462       content: "Fielding & Reschke";
     463  }
     464  @bottom-center {
     465       content: "Expires November 10, 2014";
     466  }
     467  @bottom-right {
     468       content: "[Page " counter(page) "]";
     469  }
     470}
     471
     472@page:first {
     473    @top-left {
     474      content: normal;
     475    }
     476    @top-right {
     477      content: normal;
     478    }
     479    @top-center {
     480      content: normal;
     481    }
     482}
     483</style><link rel="Contents" href="#rfc.toc">
     484      <link rel="Author" href="#rfc.authors">
     485      <link rel="Copyright" href="#rfc.copyrightnotice">
     486      <link rel="Index" href="#rfc.index">
     487      <link rel="Chapter" title="1 Introduction" href="#rfc.section.1">
     488      <link rel="Chapter" title="2 Resources" href="#rfc.section.2">
     489      <link rel="Chapter" title="3 Representations" href="#rfc.section.3">
     490      <link rel="Chapter" title="4 Request Methods" href="#rfc.section.4">
     491      <link rel="Chapter" title="5 Request Header Fields" href="#rfc.section.5">
     492      <link rel="Chapter" title="6 Response Status Codes" href="#rfc.section.6">
     493      <link rel="Chapter" title="7 Response Header Fields" href="#rfc.section.7">
     494      <link rel="Chapter" title="8 IANA Considerations" href="#rfc.section.8">
     495      <link rel="Chapter" title="9 Security Considerations" href="#rfc.section.9">
     496      <link rel="Chapter" title="10 Acknowledgments" href="#rfc.section.10">
     497      <link rel="Chapter" href="#rfc.section.11" title="11 References">
     498      <link rel="Appendix" title="A Differences between HTTP and MIME" href="#rfc.section.A">
     499      <link rel="Appendix" title="B Changes from RFC 2616" href="#rfc.section.B">
     500      <link rel="Appendix" title="C Imported ABNF" href="#rfc.section.C">
     501      <link rel="Appendix" title="D Collected ABNF" href="#rfc.section.D">
     502      <link href="p1-messaging.html" rel="prev">
     503      <link href="p4-conditional.html" rel="next">
     504      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.629, 2014/04/17 09:22:01, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
     505      <meta name="keywords" content="Hypertext Transfer Protocol, HTTP, HTTP semantics, HTTP payload, HTTP content, HTTP method, HTTP status code">
     506      <link rel="schema.dct" href="http://purl.org/dc/terms/">
     507      <meta name="dct.creator" content="Fielding, R.">
     508      <meta name="dct.creator" content="Reschke, J. F.">
     509      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest">
     510      <meta name="dct.issued" scheme="ISO8601" content="2014-05-09">
     511      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
     512      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is a stateless application-level protocol for distributed, collaborative, hypertext information systems. This document defines the semantics of HTTP/1.1 messages, as expressed by request methods, request header fields, response status codes, and response header fields, along with the payload of messages (metadata and body content) and mechanisms for content negotiation.">
     513      <meta name="description" content="The Hypertext Transfer Protocol (HTTP) is a stateless application-level protocol for distributed, collaborative, hypertext information systems. This document defines the semantics of HTTP/1.1 messages, as expressed by request methods, request header fields, response status codes, and response header fields, along with the payload of messages (metadata and body content) and mechanisms for content negotiation.">
     514   </head>
     515   <body onload="initFeedback();">
     516      <table class="header">
     517         <tbody>
     518            <tr>
     519               <td class="left">HTTPbis Working Group</td>
     520               <td class="right">R. Fielding, Editor</td>
     521            </tr>
     522            <tr>
     523               <td class="left">Internet-Draft</td>
     524               <td class="right">Adobe</td>
     525            </tr>
     526            <tr>
     527               <td class="left">Obsoletes: <a href="http://tools.ietf.org/html/rfc2616">2616</a> (if approved)
     528               </td>
     529               <td class="right">J. Reschke, Editor</td>
     530            </tr>
     531            <tr>
     532               <td class="left">Updates: <a href="http://tools.ietf.org/html/rfc2817">2817</a> (if approved)
     533               </td>
     534               <td class="right">greenbytes</td>
     535            </tr>
     536            <tr>
     537               <td class="left">Intended status: Standards Track</td>
     538               <td class="right">May 9, 2014</td>
     539            </tr>
     540            <tr>
     541               <td class="left">Expires: November 10, 2014</td>
     542               <td class="right"></td>
     543            </tr>
     544         </tbody>
     545      </table>
     546      <p class="title">Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content<br><span class="filename">draft-ietf-httpbis-p2-semantics-latest</span></p>
     547      <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1>
     548      <p>The Hypertext Transfer Protocol (HTTP) is a stateless application-level protocol for distributed, collaborative, hypertext
     549         information systems. This document defines the semantics of HTTP/1.1 messages, as expressed by request methods, request header
     550         fields, response status codes, and response header fields, along with the payload of messages (metadata and body content)
     551         and mechanisms for content negotiation.
     552      </p>
     553      <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1>
     554      <p>Discussion of this draft takes place on the HTTPBIS working group mailing list (ietf-http-wg@w3.org), which is archived at &lt;<a href="http://lists.w3.org/Archives/Public/ietf-http-wg/">http://lists.w3.org/Archives/Public/ietf-http-wg/</a>&gt;.
     555      </p>
     556      <p>The current issues list is at &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/report/3">http://tools.ietf.org/wg/httpbis/trac/report/3</a>&gt; and related documents (including fancy diffs) can be found at &lt;<a href="http://tools.ietf.org/wg/httpbis/">http://tools.ietf.org/wg/httpbis/</a>&gt;.
     557      </p>
     558      <p><em>This is a temporary document for the purpose of tracking the editorial changes made during the AUTH48 (RFC publication) phase.</em>
     559      </p>
     560      <div id="rfc.status">
     561         <h1><a href="#rfc.status">Status of This Memo</a></h1>
     562         <p>This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.</p>
     563         <p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute
     564            working documents as Internet-Drafts. The list of current Internet-Drafts is at <a href="http://datatracker.ietf.org/drafts/current/">http://datatracker.ietf.org/drafts/current/</a>.
     565         </p>
     566         <p>Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other
     567            documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as “work
     568            in progress”.
     569         </p>
     570         <p>This Internet-Draft will expire on November 10, 2014.</p>
     571      </div>
     572      <div id="rfc.copyrightnotice">
     573         <h1><a href="#rfc.copyrightnotice">Copyright Notice</a></h1>
     574         <p>Copyright © 2014 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     575         <p>This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights
     576            and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License
     577            text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified
     578            BSD License.
     579         </p>
     580         <p>This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November
     581            10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to
     582            allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s)
     583            controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative
     584            works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate
     585            it into languages other than English.
     586         </p>
     587      </div>
     588      <hr class="noprint">
     589      <h1 class="np" id="rfc.toc"><a href="#rfc.toc">Table of Contents</a></h1>
     590      <ul class="toc">
     591         <li><a href="#rfc.section.1">1.</a>&nbsp;&nbsp;&nbsp;<a href="#introduction">Introduction</a><ul>
     592               <li><a href="#rfc.section.1.1">1.1</a>&nbsp;&nbsp;&nbsp;<a href="#conformance">Conformance and Error Handling</a></li>
     593               <li><a href="#rfc.section.1.2">1.2</a>&nbsp;&nbsp;&nbsp;<a href="#notation">Syntax Notation</a></li>
     594            </ul>
     595         </li>
     596         <li><a href="#rfc.section.2">2.</a>&nbsp;&nbsp;&nbsp;<a href="#resources">Resources</a></li>
     597         <li><a href="#rfc.section.3">3.</a>&nbsp;&nbsp;&nbsp;<a href="#representations">Representations</a><ul>
     598               <li><a href="#rfc.section.3.1">3.1</a>&nbsp;&nbsp;&nbsp;<a href="#representation.metadata">Representation Metadata</a><ul>
     599                     <li><a href="#rfc.section.3.1.1">3.1.1</a>&nbsp;&nbsp;&nbsp;<a href="#data.type">Processing Representation Data</a></li>
     600                     <li><a href="#rfc.section.3.1.2">3.1.2</a>&nbsp;&nbsp;&nbsp;<a href="#data.encoding">Encoding for Compression or Integrity</a></li>
     601                     <li><a href="#rfc.section.3.1.3">3.1.3</a>&nbsp;&nbsp;&nbsp;<a href="#audience.language">Audience Language</a></li>
     602                     <li><a href="#rfc.section.3.1.4">3.1.4</a>&nbsp;&nbsp;&nbsp;<a href="#identification">Identification</a></li>
     603                  </ul>
     604               </li>
     605               <li><a href="#rfc.section.3.2">3.2</a>&nbsp;&nbsp;&nbsp;<a href="#representation.data">Representation Data</a></li>
     606               <li><a href="#rfc.section.3.3">3.3</a>&nbsp;&nbsp;&nbsp;<a href="#payload">Payload Semantics</a></li>
     607               <li><a href="#rfc.section.3.4">3.4</a>&nbsp;&nbsp;&nbsp;<a href="#content.negotiation">Content Negotiation</a><ul>
     608                     <li><a href="#rfc.section.3.4.1">3.4.1</a>&nbsp;&nbsp;&nbsp;<a href="#proactive.negotiation">Proactive Negotiation</a></li>
     609                     <li><a href="#rfc.section.3.4.2">3.4.2</a>&nbsp;&nbsp;&nbsp;<a href="#reactive.negotiation">Reactive Negotiation</a></li>
     610                  </ul>
     611               </li>
     612            </ul>
     613         </li>
     614         <li><a href="#rfc.section.4">4.</a>&nbsp;&nbsp;&nbsp;<a href="#methods">Request Methods</a><ul>
     615               <li><a href="#rfc.section.4.1">4.1</a>&nbsp;&nbsp;&nbsp;<a href="#method.overview">Overview</a></li>
     616               <li><a href="#rfc.section.4.2">4.2</a>&nbsp;&nbsp;&nbsp;<a href="#method.properties">Common Method Properties</a><ul>
     617                     <li><a href="#rfc.section.4.2.1">4.2.1</a>&nbsp;&nbsp;&nbsp;<a href="#safe.methods">Safe Methods</a></li>
     618                     <li><a href="#rfc.section.4.2.2">4.2.2</a>&nbsp;&nbsp;&nbsp;<a href="#idempotent.methods">Idempotent Methods</a></li>
     619                     <li><a href="#rfc.section.4.2.3">4.2.3</a>&nbsp;&nbsp;&nbsp;<a href="#cacheable.methods">Cacheable Methods</a></li>
     620                  </ul>
     621               </li>
     622               <li><a href="#rfc.section.4.3">4.3</a>&nbsp;&nbsp;&nbsp;<a href="#method.definitions">Method Definitions</a><ul>
     623                     <li><a href="#rfc.section.4.3.1">4.3.1</a>&nbsp;&nbsp;&nbsp;<a href="#GET">GET</a></li>
     624                     <li><a href="#rfc.section.4.3.2">4.3.2</a>&nbsp;&nbsp;&nbsp;<a href="#HEAD">HEAD</a></li>
     625                     <li><a href="#rfc.section.4.3.3">4.3.3</a>&nbsp;&nbsp;&nbsp;<a href="#POST">POST</a></li>
     626                     <li><a href="#rfc.section.4.3.4">4.3.4</a>&nbsp;&nbsp;&nbsp;<a href="#PUT">PUT</a></li>
     627                     <li><a href="#rfc.section.4.3.5">4.3.5</a>&nbsp;&nbsp;&nbsp;<a href="#DELETE">DELETE</a></li>
     628                     <li><a href="#rfc.section.4.3.6">4.3.6</a>&nbsp;&nbsp;&nbsp;<a href="#CONNECT">CONNECT</a></li>
     629                     <li><a href="#rfc.section.4.3.7">4.3.7</a>&nbsp;&nbsp;&nbsp;<a href="#OPTIONS">OPTIONS</a></li>
     630                     <li><a href="#rfc.section.4.3.8">4.3.8</a>&nbsp;&nbsp;&nbsp;<a href="#TRACE">TRACE</a></li>
     631                  </ul>
     632               </li>
     633            </ul>
     634         </li>
     635         <li><a href="#rfc.section.5">5.</a>&nbsp;&nbsp;&nbsp;<a href="#request.header.fields">Request Header Fields</a><ul>
     636               <li><a href="#rfc.section.5.1">5.1</a>&nbsp;&nbsp;&nbsp;<a href="#request.controls">Controls</a><ul>
     637                     <li><a href="#rfc.section.5.1.1">5.1.1</a>&nbsp;&nbsp;&nbsp;<a href="#header.expect">Expect</a></li>
     638                     <li><a href="#rfc.section.5.1.2">5.1.2</a>&nbsp;&nbsp;&nbsp;<a href="#header.max-forwards">Max-Forwards</a></li>
     639                  </ul>
     640               </li>
     641               <li><a href="#rfc.section.5.2">5.2</a>&nbsp;&nbsp;&nbsp;<a href="#request.conditionals">Conditionals</a></li>
     642               <li><a href="#rfc.section.5.3">5.3</a>&nbsp;&nbsp;&nbsp;<a href="#request.conneg">Content Negotiation</a><ul>
     643                     <li><a href="#rfc.section.5.3.1">5.3.1</a>&nbsp;&nbsp;&nbsp;<a href="#quality.values">Quality Values</a></li>
     644                     <li><a href="#rfc.section.5.3.2">5.3.2</a>&nbsp;&nbsp;&nbsp;<a href="#header.accept">Accept</a></li>
     645                     <li><a href="#rfc.section.5.3.3">5.3.3</a>&nbsp;&nbsp;&nbsp;<a href="#header.accept-charset">Accept-Charset</a></li>
     646                     <li><a href="#rfc.section.5.3.4">5.3.4</a>&nbsp;&nbsp;&nbsp;<a href="#header.accept-encoding">Accept-Encoding</a></li>
     647                     <li><a href="#rfc.section.5.3.5">5.3.5</a>&nbsp;&nbsp;&nbsp;<a href="#header.accept-language">Accept-Language</a></li>
     648                  </ul>
     649               </li>
     650               <li><a href="#rfc.section.5.4">5.4</a>&nbsp;&nbsp;&nbsp;<a href="#request.auth">Authentication Credentials</a></li>
     651               <li><a href="#rfc.section.5.5">5.5</a>&nbsp;&nbsp;&nbsp;<a href="#request.context">Request Context</a><ul>
     652                     <li><a href="#rfc.section.5.5.1">5.5.1</a>&nbsp;&nbsp;&nbsp;<a href="#header.from">From</a></li>
     653                     <li><a href="#rfc.section.5.5.2">5.5.2</a>&nbsp;&nbsp;&nbsp;<a href="#header.referer">Referer</a></li>
     654                     <li><a href="#rfc.section.5.5.3">5.5.3</a>&nbsp;&nbsp;&nbsp;<a href="#header.user-agent">User-Agent</a></li>
     655                  </ul>
     656               </li>
     657            </ul>
     658         </li>
     659         <li><a href="#rfc.section.6">6.</a>&nbsp;&nbsp;&nbsp;<a href="#status.codes">Response Status Codes</a><ul>
     660               <li><a href="#rfc.section.6.1">6.1</a>&nbsp;&nbsp;&nbsp;<a href="#overview.of.status.codes">Overview of Status Codes</a></li>
     661               <li><a href="#rfc.section.6.2">6.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.1xx">Informational 1xx</a><ul>
     662                     <li><a href="#rfc.section.6.2.1">6.2.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.100">100 Continue</a></li>
     663                     <li><a href="#rfc.section.6.2.2">6.2.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.101">101 Switching Protocols</a></li>
     664                  </ul>
     665               </li>
     666               <li><a href="#rfc.section.6.3">6.3</a>&nbsp;&nbsp;&nbsp;<a href="#status.2xx">Successful 2xx</a><ul>
     667                     <li><a href="#rfc.section.6.3.1">6.3.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.200">200 OK</a></li>
     668                     <li><a href="#rfc.section.6.3.2">6.3.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.201">201 Created</a></li>
     669                     <li><a href="#rfc.section.6.3.3">6.3.3</a>&nbsp;&nbsp;&nbsp;<a href="#status.202">202 Accepted</a></li>
     670                     <li><a href="#rfc.section.6.3.4">6.3.4</a>&nbsp;&nbsp;&nbsp;<a href="#status.203">203 Non-Authoritative Information</a></li>
     671                     <li><a href="#rfc.section.6.3.5">6.3.5</a>&nbsp;&nbsp;&nbsp;<a href="#status.204">204 No Content</a></li>
     672                     <li><a href="#rfc.section.6.3.6">6.3.6</a>&nbsp;&nbsp;&nbsp;<a href="#status.205">205 Reset Content</a></li>
     673                  </ul>
     674               </li>
     675               <li><a href="#rfc.section.6.4">6.4</a>&nbsp;&nbsp;&nbsp;<a href="#status.3xx">Redirection 3xx</a><ul>
     676                     <li><a href="#rfc.section.6.4.1">6.4.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.300">300 Multiple Choices</a></li>
     677                     <li><a href="#rfc.section.6.4.2">6.4.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.301">301 Moved Permanently</a></li>
     678                     <li><a href="#rfc.section.6.4.3">6.4.3</a>&nbsp;&nbsp;&nbsp;<a href="#status.302">302 Found</a></li>
     679                     <li><a href="#rfc.section.6.4.4">6.4.4</a>&nbsp;&nbsp;&nbsp;<a href="#status.303">303 See Other</a></li>
     680                     <li><a href="#rfc.section.6.4.5">6.4.5</a>&nbsp;&nbsp;&nbsp;<a href="#status.305">305 Use Proxy</a></li>
     681                     <li><a href="#rfc.section.6.4.6">6.4.6</a>&nbsp;&nbsp;&nbsp;<a href="#status.306">306 (Unused)</a></li>
     682                     <li><a href="#rfc.section.6.4.7">6.4.7</a>&nbsp;&nbsp;&nbsp;<a href="#status.307">307 Temporary Redirect</a></li>
     683                  </ul>
     684               </li>
     685               <li><a href="#rfc.section.6.5">6.5</a>&nbsp;&nbsp;&nbsp;<a href="#status.4xx">Client Error 4xx</a><ul>
     686                     <li><a href="#rfc.section.6.5.1">6.5.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.400">400 Bad Request</a></li>
     687                     <li><a href="#rfc.section.6.5.2">6.5.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.402">402 Payment Required</a></li>
     688                     <li><a href="#rfc.section.6.5.3">6.5.3</a>&nbsp;&nbsp;&nbsp;<a href="#status.403">403 Forbidden</a></li>
     689                     <li><a href="#rfc.section.6.5.4">6.5.4</a>&nbsp;&nbsp;&nbsp;<a href="#status.404">404 Not Found</a></li>
     690                     <li><a href="#rfc.section.6.5.5">6.5.5</a>&nbsp;&nbsp;&nbsp;<a href="#status.405">405 Method Not Allowed</a></li>
     691                     <li><a href="#rfc.section.6.5.6">6.5.6</a>&nbsp;&nbsp;&nbsp;<a href="#status.406">406 Not Acceptable</a></li>
     692                     <li><a href="#rfc.section.6.5.7">6.5.7</a>&nbsp;&nbsp;&nbsp;<a href="#status.408">408 Request Timeout</a></li>
     693                     <li><a href="#rfc.section.6.5.8">6.5.8</a>&nbsp;&nbsp;&nbsp;<a href="#status.409">409 Conflict</a></li>
     694                     <li><a href="#rfc.section.6.5.9">6.5.9</a>&nbsp;&nbsp;&nbsp;<a href="#status.410">410 Gone</a></li>
     695                     <li><a href="#rfc.section.6.5.10">6.5.10</a>&nbsp;&nbsp;&nbsp;<a href="#status.411">411 Length Required</a></li>
     696                     <li><a href="#rfc.section.6.5.11">6.5.11</a>&nbsp;&nbsp;&nbsp;<a href="#status.413">413 Payload Too Large</a></li>
     697                     <li><a href="#rfc.section.6.5.12">6.5.12</a>&nbsp;&nbsp;&nbsp;<a href="#status.414">414 URI Too Long</a></li>
     698                     <li><a href="#rfc.section.6.5.13">6.5.13</a>&nbsp;&nbsp;&nbsp;<a href="#status.415">415 Unsupported Media Type</a></li>
     699                     <li><a href="#rfc.section.6.5.14">6.5.14</a>&nbsp;&nbsp;&nbsp;<a href="#status.417">417 Expectation Failed</a></li>
     700                     <li><a href="#rfc.section.6.5.15">6.5.15</a>&nbsp;&nbsp;&nbsp;<a href="#status.426">426 Upgrade Required</a></li>
     701                  </ul>
     702               </li>
     703               <li><a href="#rfc.section.6.6">6.6</a>&nbsp;&nbsp;&nbsp;<a href="#status.5xx">Server Error 5xx</a><ul>
     704                     <li><a href="#rfc.section.6.6.1">6.6.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.500">500 Internal Server Error</a></li>
     705                     <li><a href="#rfc.section.6.6.2">6.6.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.501">501 Not Implemented</a></li>
     706                     <li><a href="#rfc.section.6.6.3">6.6.3</a>&nbsp;&nbsp;&nbsp;<a href="#status.502">502 Bad Gateway</a></li>
     707                     <li><a href="#rfc.section.6.6.4">6.6.4</a>&nbsp;&nbsp;&nbsp;<a href="#status.503">503 Service Unavailable</a></li>
     708                     <li><a href="#rfc.section.6.6.5">6.6.5</a>&nbsp;&nbsp;&nbsp;<a href="#status.504">504 Gateway Timeout</a></li>
     709                     <li><a href="#rfc.section.6.6.6">6.6.6</a>&nbsp;&nbsp;&nbsp;<a href="#status.505">505 HTTP Version Not Supported</a></li>
     710                  </ul>
     711               </li>
     712            </ul>
     713         </li>
     714         <li><a href="#rfc.section.7">7.</a>&nbsp;&nbsp;&nbsp;<a href="#response.header.fields">Response Header Fields</a><ul>
     715               <li><a href="#rfc.section.7.1">7.1</a>&nbsp;&nbsp;&nbsp;<a href="#response.control.data">Control Data</a><ul>
     716                     <li><a href="#rfc.section.7.1.1">7.1.1</a>&nbsp;&nbsp;&nbsp;<a href="#origination.date">Origination Date</a></li>
     717                     <li><a href="#rfc.section.7.1.2">7.1.2</a>&nbsp;&nbsp;&nbsp;<a href="#header.location">Location</a></li>
     718                     <li><a href="#rfc.section.7.1.3">7.1.3</a>&nbsp;&nbsp;&nbsp;<a href="#header.retry-after">Retry-After</a></li>
     719                     <li><a href="#rfc.section.7.1.4">7.1.4</a>&nbsp;&nbsp;&nbsp;<a href="#header.vary">Vary</a></li>
     720                  </ul>
     721               </li>
     722               <li><a href="#rfc.section.7.2">7.2</a>&nbsp;&nbsp;&nbsp;<a href="#response.validator">Validator Header Fields</a></li>
     723               <li><a href="#rfc.section.7.3">7.3</a>&nbsp;&nbsp;&nbsp;<a href="#response.auth">Authentication Challenges</a></li>
     724               <li><a href="#rfc.section.7.4">7.4</a>&nbsp;&nbsp;&nbsp;<a href="#response.context">Response Context</a><ul>
     725                     <li><a href="#rfc.section.7.4.1">7.4.1</a>&nbsp;&nbsp;&nbsp;<a href="#header.allow">Allow</a></li>
     726                     <li><a href="#rfc.section.7.4.2">7.4.2</a>&nbsp;&nbsp;&nbsp;<a href="#header.server">Server</a></li>
     727                  </ul>
     728               </li>
     729            </ul>
     730         </li>
     731         <li><a href="#rfc.section.8">8.</a>&nbsp;&nbsp;&nbsp;<a href="#IANA.considerations">IANA Considerations</a><ul>
     732               <li><a href="#rfc.section.8.1">8.1</a>&nbsp;&nbsp;&nbsp;<a href="#method.registry">Method Registry</a><ul>
     733                     <li><a href="#rfc.section.8.1.1">8.1.1</a>&nbsp;&nbsp;&nbsp;<a href="#method.registry.procedure">Procedure</a></li>
     734                     <li><a href="#rfc.section.8.1.2">8.1.2</a>&nbsp;&nbsp;&nbsp;<a href="#considerations.for.new.methods">Considerations for New Methods</a></li>
     735                     <li><a href="#rfc.section.8.1.3">8.1.3</a>&nbsp;&nbsp;&nbsp;<a href="#method.registration">Registrations</a></li>
     736                  </ul>
     737               </li>
     738               <li><a href="#rfc.section.8.2">8.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.code.registry">Status Code Registry</a><ul>
     739                     <li><a href="#rfc.section.8.2.1">8.2.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.code.registry.procedure">Procedure</a></li>
     740                     <li><a href="#rfc.section.8.2.2">8.2.2</a>&nbsp;&nbsp;&nbsp;<a href="#considerations.for.new.status.codes">Considerations for New Status Codes</a></li>
     741                     <li><a href="#rfc.section.8.2.3">8.2.3</a>&nbsp;&nbsp;&nbsp;<a href="#status.code.registration">Registrations</a></li>
     742                  </ul>
     743               </li>
     744               <li><a href="#rfc.section.8.3">8.3</a>&nbsp;&nbsp;&nbsp;<a href="#header.field.registry">Header Field Registry</a><ul>
     745                     <li><a href="#rfc.section.8.3.1">8.3.1</a>&nbsp;&nbsp;&nbsp;<a href="#considerations.for.new.header.fields">Considerations for New Header Fields</a></li>
     746                     <li><a href="#rfc.section.8.3.2">8.3.2</a>&nbsp;&nbsp;&nbsp;<a href="#header.field.registration">Registrations</a></li>
     747                  </ul>
     748               </li>
     749               <li><a href="#rfc.section.8.4">8.4</a>&nbsp;&nbsp;&nbsp;<a href="#content.coding.registry">Content Coding Registry</a><ul>
     750                     <li><a href="#rfc.section.8.4.1">8.4.1</a>&nbsp;&nbsp;&nbsp;<a href="#content.coding.procedure">Procedure</a></li>
     751                     <li><a href="#rfc.section.8.4.2">8.4.2</a>&nbsp;&nbsp;&nbsp;<a href="#content.coding.registration">Registrations</a></li>
     752                  </ul>
     753               </li>
     754            </ul>
     755         </li>
     756         <li><a href="#rfc.section.9">9.</a>&nbsp;&nbsp;&nbsp;<a href="#security.considerations">Security Considerations</a><ul>
     757               <li><a href="#rfc.section.9.1">9.1</a>&nbsp;&nbsp;&nbsp;<a href="#attack.pathname">Attacks Based on File and Path Names</a></li>
     758               <li><a href="#rfc.section.9.2">9.2</a>&nbsp;&nbsp;&nbsp;<a href="#attack.injection">Attacks Based on Command, Code, or Query Injection</a></li>
     759               <li><a href="#rfc.section.9.3">9.3</a>&nbsp;&nbsp;&nbsp;<a href="#personal.information">Disclosure of Personal Information</a></li>
     760               <li><a href="#rfc.section.9.4">9.4</a>&nbsp;&nbsp;&nbsp;<a href="#sensitive.information.in.uris">Disclosure of Sensitive Information in URIs</a></li>
     761               <li><a href="#rfc.section.9.5">9.5</a>&nbsp;&nbsp;&nbsp;<a href="#fragment.disclosure">Disclosure of Fragment after Redirects</a></li>
     762               <li><a href="#rfc.section.9.6">9.6</a>&nbsp;&nbsp;&nbsp;<a href="#disclosure.product.information">Disclosure of Product Information</a></li>
     763               <li><a href="#rfc.section.9.7">9.7</a>&nbsp;&nbsp;&nbsp;<a href="#fingerprinting">Browser Fingerprinting</a></li>
     764            </ul>
     765         </li>
     766         <li><a href="#rfc.section.10">10.</a>&nbsp;&nbsp;&nbsp;<a href="#acks">Acknowledgments</a></li>
     767         <li><a href="#rfc.section.11">11.</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references">References</a><ul>
     768               <li><a href="#rfc.section.11.1">11.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references.1">Normative References</a></li>
     769               <li><a href="#rfc.section.11.2">11.2</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references.2">Informative References</a></li>
     770            </ul>
     771         </li>
     772         <li><a href="#rfc.section.A">A.</a>&nbsp;&nbsp;&nbsp;<a href="#differences.between.http.and.mime">Differences between HTTP and MIME</a><ul>
     773               <li><a href="#rfc.section.A.1">A.1</a>&nbsp;&nbsp;&nbsp;<a href="#mime-version">MIME-Version</a></li>
     774               <li><a href="#rfc.section.A.2">A.2</a>&nbsp;&nbsp;&nbsp;<a href="#conversion.to.canonical.form">Conversion to Canonical Form</a></li>
     775               <li><a href="#rfc.section.A.3">A.3</a>&nbsp;&nbsp;&nbsp;<a href="#conversion.of.date.formats">Conversion of Date Formats</a></li>
     776               <li><a href="#rfc.section.A.4">A.4</a>&nbsp;&nbsp;&nbsp;<a href="#conversion.content-encoding">Conversion of Content-Encoding</a></li>
     777               <li><a href="#rfc.section.A.5">A.5</a>&nbsp;&nbsp;&nbsp;<a href="#conversion.content-transfer-encoding">Conversion of Content-Transfer-Encoding</a></li>
     778               <li><a href="#rfc.section.A.6">A.6</a>&nbsp;&nbsp;&nbsp;<a href="#mhtml.line.length">MHTML and Line Length Limitations</a></li>
     779            </ul>
     780         </li>
     781         <li><a href="#rfc.section.B">B.</a>&nbsp;&nbsp;&nbsp;<a href="#changes.from.rfc.2616">Changes from RFC 2616</a></li>
     782         <li><a href="#rfc.section.C">C.</a>&nbsp;&nbsp;&nbsp;<a href="#imported.abnf">Imported ABNF</a></li>
     783         <li><a href="#rfc.section.D">D.</a>&nbsp;&nbsp;&nbsp;<a href="#collected.abnf">Collected ABNF</a></li>
     784         <li><a href="#rfc.index">Index</a></li>
     785         <li><a href="#rfc.authors">Authors' Addresses</a></li>
     786      </ul>
     787      <div id="introduction">
     788         <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;<a href="#introduction">Introduction</a></h1>
     789         <p id="rfc.section.1.p.1">Each Hypertext Transfer Protocol (HTTP) message is either a request or a response. A server listens on a connection for a
     790            request, parses each message received, interprets the message semantics in relation to the identified request target, and
     791            responds to that request with one or more response messages. A client constructs request messages to communicate specific
     792            intentions, examines received responses to see if the intentions were carried out, and determines how to interpret the results.
     793            This document defines HTTP/1.1 request and response semantics in terms of the architecture defined in <a href="#RFC7230" id="rfc.xref.RFC7230.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>.
     794         </p>
     795         <p id="rfc.section.1.p.2">HTTP provides a uniform interface for interacting with a resource (<a href="#resources" title="Resources">Section&nbsp;2</a>), regardless of its type, nature, or implementation, via the manipulation and transfer of representations (<a href="#representations" title="Representations">Section&nbsp;3</a>).
     796         </p>
     797         <p id="rfc.section.1.p.3">HTTP semantics include the intentions defined by each request method (<a href="#methods" title="Request Methods">Section&nbsp;4</a>), extensions to those semantics that might be described in request header fields (<a href="#request.header.fields" title="Request Header Fields">Section&nbsp;5</a>), the meaning of status codes to indicate a machine-readable response (<a href="#status.codes" title="Response Status Codes">Section&nbsp;6</a>), and the meaning of other control data and resource metadata that might be given in response header fields (<a href="#response.header.fields" title="Response Header Fields">Section&nbsp;7</a>).
     798         </p>
     799         <p id="rfc.section.1.p.4"><span id="rfc.iref.c.1"></span> This document also defines representation metadata that describe how a payload is intended to be interpreted by a recipient,
     800            the request header fields that might influence content selection, and the various selection algorithms that are collectively
     801            referred to as "<dfn>content negotiation</dfn>" (<a href="#content.negotiation" title="Content Negotiation">Section&nbsp;3.4</a>).
     802         </p>
     803         <div id="conformance">
     804            <h2 id="rfc.section.1.1"><a href="#rfc.section.1.1">1.1</a>&nbsp;<a href="#conformance">Conformance and Error Handling</a></h2>
     805            <p id="rfc.section.1.1.p.1">The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL"
     806               in this document are to be interpreted as described in <a href="#RFC2119" id="rfc.xref.RFC2119.1"><cite title="Key words for use in RFCs to Indicate Requirement Levels">[RFC2119]</cite></a>.
     807            </p>
     808            <p id="rfc.section.1.1.p.2">Conformance criteria and considerations regarding error handling are defined in <a href="p1-messaging.html#conformance" title="Conformance and Error Handling">Section 2.5</a> of <a href="#RFC7230" id="rfc.xref.RFC7230.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>.
     809            </p>
     810         </div>
     811         <div id="notation">
     812            <h2 id="rfc.section.1.2"><a href="#rfc.section.1.2">1.2</a>&nbsp;<a href="#notation">Syntax Notation</a></h2>
     813            <p id="rfc.section.1.2.p.1">This specification uses the Augmented Backus-Naur Form (ABNF) notation of <a href="#RFC5234" id="rfc.xref.RFC5234.1"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a> with a list extension, defined in <a href="p1-messaging.html#abnf.extension" title="ABNF List Extension: #rule">Section 7</a> of <a href="#RFC7230" id="rfc.xref.RFC7230.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>, that allows for compact definition of comma-separated lists using a '#' operator (similar to how the '*' operator indicates
     814               repetition). <a href="#imported.abnf" title="Imported ABNF">Appendix&nbsp;C</a> describes rules imported from other documents. <a href="#collected.abnf" title="Collected ABNF">Appendix&nbsp;D</a> shows the collected grammar with all list operators expanded to standard ABNF notation.
     815            </p>
     816            <p id="rfc.section.1.2.p.2">This specification uses the terms "character", "character encoding scheme", "charset", and "protocol element" as they are
     817               defined in <a href="#RFC6365" id="rfc.xref.RFC6365.1"><cite title="Terminology Used in Internationalization in the IETF">[RFC6365]</cite></a>.
     818            </p>
     819         </div>
     820      </div>
     821      <div id="resources">
     822         <h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;<a href="#resources">Resources</a></h1>
     823         <p id="rfc.section.2.p.1">The target of an HTTP request is called a "<dfn>resource</dfn>". HTTP does not limit the nature of a resource; it merely defines an interface that might be used to interact with resources.
     824            Each resource is identified by a Uniform Resource Identifier (URI), as described in <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.7</a> of <a href="#RFC7230" id="rfc.xref.RFC7230.4"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>.
     825         </p>
     826         <p id="rfc.section.2.p.2">When a client constructs an HTTP/1.1 request message, it sends the <a href="p1-messaging.html#target-resource" class="smpl">target URI</a> in one of various forms, as defined in (<a href="p1-messaging.html#request-target" title="Request Target">Section 5.3</a> of <a href="#RFC7230" id="rfc.xref.RFC7230.5"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>). When a request is received, the server reconstructs an <a href="p1-messaging.html#effective.request.uri" class="smpl">effective request URI</a> for the target resource (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 5.5</a> of <a href="#RFC7230" id="rfc.xref.RFC7230.6"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>).
     827         </p>
     828         <p id="rfc.section.2.p.3">One design goal of HTTP is to separate resource identification from request semantics, which is made possible by vesting the
     829            request semantics in the request method (<a href="#methods" title="Request Methods">Section&nbsp;4</a>) and a few request-modifying header fields (<a href="#request.header.fields" title="Request Header Fields">Section&nbsp;5</a>). If there is a conflict between the method semantics and any semantic implied by the URI itself, as described in <a href="#safe.methods" title="Safe Methods">Section&nbsp;4.2.1</a>, the method semantics take precedence.
     830         </p>
     831      </div>
     832      <div id="representations">
     833         <div id="rfc.iref.r.1"></div>
     834         <div id="rfc.iref.s.1"></div>
     835         <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;<a href="#representations">Representations</a></h1>
     836         <p id="rfc.section.3.p.1">Considering that a resource could be anything, and that the uniform interface provided by HTTP is similar to a window through
     837            which one can observe and act upon such a thing only through the communication of messages to some independent actor on the
     838            other side, an abstraction is needed to represent ("take the place of") the current or desired state of that thing in our
     839            communications. That abstraction is called a representation <a href="#REST" id="rfc.xref.REST.1"><cite title="Architectural Styles and the Design of Network-based Software Architectures">[REST]</cite></a>.
     840         </p>
     841         <p id="rfc.section.3.p.2">For the purposes of HTTP, a "<dfn>representation</dfn>" is information that is intended to reflect a past, current, or desired state of a given resource, in a format that can be
     842            readily communicated via the protocol, and that consists of a set of representation metadata and a potentially unbounded stream
     843            of representation data.
     844         </p>
     845         <p id="rfc.section.3.p.3">An origin server might be provided with, or be capable of generating, multiple representations that are each intended to reflect
     846            the current state of a <a href="#resources" class="smpl">target resource</a>. In such cases, some algorithm is used by the origin server to select one of those representations as most applicable to
     847            a given request, usually based on <a href="#content.negotiation" class="smpl">content negotiation</a>. This "<dfn>selected representation</dfn>" is used to provide the data and metadata for evaluating conditional requests <a href="#RFC7232" id="rfc.xref.RFC7232.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[RFC7232]</cite></a> and constructing the payload for <a href="#status.200" class="smpl">200 (OK)</a> and <a href="p4-conditional.html#status.304" class="smpl">304 (Not Modified)</a> responses to GET (<a href="#GET" id="rfc.xref.GET.1" title="GET">Section&nbsp;4.3.1</a>).
     848         </p>
     849         <div id="representation.metadata">
     850            <h2 id="rfc.section.3.1"><a href="#rfc.section.3.1">3.1</a>&nbsp;<a href="#representation.metadata">Representation Metadata</a></h2>
     851            <p id="rfc.section.3.1.p.1">Representation header fields provide metadata about the representation. When a message includes a payload body, the representation
     852               header fields describe how to interpret the representation data enclosed in the payload body. In a response to a HEAD request,
     853               the representation header fields describe the representation data that would have been enclosed in the payload body if the
     854               same request had been a GET.
     855            </p>
     856            <p id="rfc.section.3.1.p.2">The following header fields convey representation metadata:</p>
     857            <div id="rfc.table.u.1">
     858               <table class="tt full left" cellpadding="3" cellspacing="0">
     859                  <thead>
     860                     <tr>
     861                        <th>Header Field Name</th>
     862                        <th>Defined in...</th>
     863                     </tr>
     864                  </thead>
     865                  <tbody>
     866                     <tr>
     867                        <td class="left">Content-Type</td>
     868                        <td class="left"><a href="#header.content-type" id="rfc.xref.header.content-type.1" title="Content-Type">Section&nbsp;3.1.1.5</a></td>
     869                     </tr>
     870                     <tr>
     871                        <td class="left">Content-Encoding</td>
     872                        <td class="left"><a href="#header.content-encoding" id="rfc.xref.header.content-encoding.1" title="Content-Encoding">Section&nbsp;3.1.2.2</a></td>
     873                     </tr>
     874                     <tr>
     875                        <td class="left">Content-Language</td>
     876                        <td class="left"><a href="#header.content-language" id="rfc.xref.header.content-language.1" title="Content-Language">Section&nbsp;3.1.3.2</a></td>
     877                     </tr>
     878                     <tr>
     879                        <td class="left">Content-Location</td>
     880                        <td class="left"><a href="#header.content-location" id="rfc.xref.header.content-location.1" title="Content-Location">Section&nbsp;3.1.4.2</a></td>
     881                     </tr>
     882                  </tbody>
     883               </table>
     884            </div>
     885            <div id="data.type">
     886               <h3 id="rfc.section.3.1.1"><a href="#rfc.section.3.1.1">3.1.1</a>&nbsp;<a href="#data.type">Processing Representation Data</a></h3>
     887               <div id="media.type">
     888                  <h4 id="rfc.section.3.1.1.1"><a href="#rfc.section.3.1.1.1">3.1.1.1</a>&nbsp;<a href="#media.type">Media Type</a></h4>
     889                  <p id="rfc.section.3.1.1.1.p.1">HTTP uses Internet media types <a href="#RFC2046" id="rfc.xref.RFC2046.1"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types">[RFC2046]</cite></a> in the <a href="#header.content-type" class="smpl">Content-Type</a> (<a href="#header.content-type" id="rfc.xref.header.content-type.2" title="Content-Type">Section&nbsp;3.1.1.5</a>) and <a href="#header.accept" class="smpl">Accept</a> (<a href="#header.accept" id="rfc.xref.header.accept.1" title="Accept">Section&nbsp;5.3.2</a>) header fields in order to provide open and extensible data typing and type negotiation. Media types define both a data format
     890                     and various processing models: how to process that data in accordance with each context in which it is received.
     891                  </p>
     892                  <div id="rfc.figure.u.1"></div><pre class="inline"><span id="rfc.iref.g.1"></span><span id="rfc.iref.g.2"></span><span id="rfc.iref.g.3"></span>  <a href="#media.type" class="smpl">media-type</a> = <a href="#media.type" class="smpl">type</a> "/" <a href="#media.type" class="smpl">subtype</a> *( <a href="#imported.abnf" class="smpl">OWS</a> ";" <a href="#imported.abnf" class="smpl">OWS</a> <a href="#rule.parameter" class="smpl">parameter</a> )
     893  <a href="#media.type" class="smpl">type</a>       = <a href="#imported.abnf" class="smpl">token</a>
     894  <a href="#media.type" class="smpl">subtype</a>    = <a href="#imported.abnf" class="smpl">token</a>
     895</pre><div id="rule.parameter">
     896                     <p id="rfc.section.3.1.1.1.p.3"> The type/subtype <em class="bcp14">MAY</em> be followed by parameters in the form of name=value pairs.
     897                     </p>
     898                  </div>
     899                  <div id="rfc.figure.u.2"></div><pre class="inline"><span id="rfc.iref.g.4"></span>  <a href="#rule.parameter" class="smpl">parameter</a>      = <a href="#imported.abnf" class="smpl">token</a> "=" ( <a href="#imported.abnf" class="smpl">token</a> / <a href="#imported.abnf" class="smpl">quoted-string</a> )
     900</pre><p id="rfc.section.3.1.1.1.p.5">The type, subtype, and parameter name tokens are case-insensitive. Parameter values might or might not be case-sensitive,
     901                     depending on the semantics of the parameter name. The presence or absence of a parameter might be significant to the processing
     902                     of a media-type, depending on its definition within the media type registry.
     903                  </p>
     904                  <p id="rfc.section.3.1.1.1.p.6">A parameter value that matches the <a href="#imported.abnf" class="smpl">token</a> production can be transmitted either as a token or within a quoted-string. The quoted and unquoted values are equivalent.
     905                     For example, the following examples are all equivalent, but the first is preferred for consistency:
     906                  </p>
     907                  <div id="rfc.figure.u.3"></div><pre class="text">  text/html;charset=utf-8
     908  text/html;charset=UTF-8
     909  Text/HTML;Charset="utf-8"
     910  text/html; charset="utf-8"
     911</pre><p id="rfc.section.3.1.1.1.p.8">Internet media types ought to be registered with IANA according to the procedures defined in <a href="#BCP13" id="rfc.xref.BCP13.1"><cite title="Media Type Specifications and Registration Procedures">[BCP13]</cite></a>.
     912                  </p>
     913                  <div class="note" id="rfc.section.3.1.1.1.p.9">
     914                     <p><b>Note:</b> Unlike some similar constructs in other header fields, media type parameters do not allow whitespace (even "bad" whitespace)
     915                        around the "=" character.
     916                     </p>
     917                  </div>
     918               </div>
     919               <div id="charset">
     920                  <h4 id="rfc.section.3.1.1.2"><a href="#rfc.section.3.1.1.2">3.1.1.2</a>&nbsp;<a href="#charset">Charset</a></h4>
     921                  <p id="rfc.section.3.1.1.2.p.1">HTTP uses <dfn>charset</dfn> names to indicate or negotiate the character encoding scheme of a textual representation <a href="#RFC6365" id="rfc.xref.RFC6365.2"><cite title="Terminology Used in Internationalization in the IETF">[RFC6365]</cite></a>. A charset is identified by a case-insensitive token.
     922                  </p>
     923                  <div id="rfc.figure.u.4"></div><pre class="inline"><span id="rfc.iref.g.5"></span>  <a href="#charset" class="smpl">charset</a> = <a href="#imported.abnf" class="smpl">token</a>
     924</pre><p id="rfc.section.3.1.1.2.p.3">Charset names ought to be registered in the IANA "Character Sets" registry (&lt;<a href="http://www.iana.org/assignments/character-sets">http://www.iana.org/assignments/character-sets</a>&gt;) according to the procedures defined in <a href="#RFC2978" id="rfc.xref.RFC2978.1"><cite title="IANA Charset Registration Procedures">[RFC2978]</cite></a>.
     925                  </p>
     926               </div>
     927               <div id="canonicalization.and.text.defaults">
     928                  <h4 id="rfc.section.3.1.1.3"><a href="#rfc.section.3.1.1.3">3.1.1.3</a>&nbsp;<a href="#canonicalization.and.text.defaults">Canonicalization and Text Defaults</a></h4>
     929                  <p id="rfc.section.3.1.1.3.p.1">Internet media types are registered with a canonical form in order to be interoperable among systems with varying native encoding
     930                     formats. Representations selected or transferred via HTTP ought to be in canonical form, for many of the same reasons described
     931                     by the Multipurpose Internet Mail Extensions (MIME) <a href="#RFC2045" id="rfc.xref.RFC2045.1"><cite title="Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies">[RFC2045]</cite></a>. However, the performance characteristics of email deployments (i.e., store and forward messages to peers) are significantly
     932                     different from those common to HTTP and the Web (server-based information services). Furthermore, MIME's constraints for the
     933                     sake of compatibility with older mail transfer protocols do not apply to HTTP (see <a href="#differences.between.http.and.mime" title="Differences between HTTP and MIME">Appendix&nbsp;A</a>).
     934                  </p>
     935                  <p id="rfc.section.3.1.1.3.p.2">MIME's canonical form requires that media subtypes of the "text" type use CRLF as the text line break. HTTP allows the transfer
     936                     of text media with plain CR or LF alone representing a line break, when such line breaks are consistent for an entire representation.
     937                     An HTTP sender <em class="bcp14">MAY</em> generate, and a recipient <em class="bcp14">MUST</em> be able to parse, line breaks in text media that consist of CRLF, bare CR, or bare LF. In addition, text media in HTTP is
     938                     not limited to charsets that use octets 13 and 10 for CR and LF, respectively. This flexibility regarding line breaks applies
     939                     only to text within a representation that has been assigned a "text" media type; it does not apply to "multipart" types or
     940                     HTTP elements outside the payload body (e.g., header fields).
     941                  </p>
     942                  <p id="rfc.section.3.1.1.3.p.3">If a representation is encoded with a content-coding, the underlying data ought to be in a form defined above prior to being
     943                     encoded.
     944                  </p>
     945               </div>
     946               <div id="multipart.types">
     947                  <h4 id="rfc.section.3.1.1.4"><a href="#rfc.section.3.1.1.4">3.1.1.4</a>&nbsp;<a href="#multipart.types">Multipart Types</a></h4>
     948                  <p id="rfc.section.3.1.1.4.p.1">MIME provides for a number of "multipart" types — encapsulations of one or more representations within a single message body.
     949                     All multipart types share a common syntax, as defined in <a href="http://tools.ietf.org/html/rfc2046#section-5.1.1">Section 5.1.1</a> of <a href="#RFC2046" id="rfc.xref.RFC2046.2"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types">[RFC2046]</cite></a>, and include a boundary parameter as part of the media type value. The message body is itself a protocol element; a sender <em class="bcp14">MUST</em> generate only CRLF to represent line breaks between body parts.
     950                  </p>
     951                  <p id="rfc.section.3.1.1.4.p.2">HTTP message framing does not use the multipart boundary as an indicator of message body length, though it might be used by
     952                     implementations that generate or process the payload. For example, the "multipart/form-data" type is often used for carrying
     953                     form data in a request, as described in <a href="#RFC2388" id="rfc.xref.RFC2388.1"><cite title="Returning Values from Forms: multipart/form-data">[RFC2388]</cite></a>, and the "multipart/byteranges" type is defined by this specification for use in some <a href="p5-range.html#status.206" class="smpl">206 (Partial Content)</a> responses <a href="#RFC7233" id="rfc.xref.RFC7233.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Range Requests">[RFC7233]</cite></a>.
     954                  </p>
     955               </div>
     956               <div id="header.content-type">
     957                  <div id="rfc.iref.c.2"></div>
     958                  <h4 id="rfc.section.3.1.1.5"><a href="#rfc.section.3.1.1.5">3.1.1.5</a>&nbsp;<a href="#header.content-type">Content-Type</a></h4>
     959                  <p id="rfc.section.3.1.1.5.p.1">The "Content-Type" header field indicates the media type of the associated representation: either the representation enclosed
     960                     in the message payload or the <a href="#representations" class="smpl">selected representation</a>, as determined by the message semantics. The indicated media type defines both the data format and how that data is intended
     961                     to be processed by a recipient, within the scope of the received message semantics, after any content codings indicated by <a href="#header.content-encoding" class="smpl">Content-Encoding</a> are decoded.
     962                  </p>
     963                  <div id="rfc.figure.u.5"></div><pre class="inline"><span id="rfc.iref.g.6"></span>  <a href="#header.content-type" class="smpl">Content-Type</a> = <a href="#media.type" class="smpl">media-type</a>
     964</pre><p id="rfc.section.3.1.1.5.p.3">Media types are defined in <a href="#media.type" title="Media Type">Section&nbsp;3.1.1.1</a>. An example of the field is
     965                  </p>
     966                  <div id="rfc.figure.u.6"></div><pre class="text">  Content-Type: text/html; charset=ISO-8859-4
     967</pre><p id="rfc.section.3.1.1.5.p.5">A sender that generates a message containing a payload body <em class="bcp14">SHOULD</em> generate a Content-Type header field in that message unless the intended media type of the enclosed representation is unknown
     968                     to the sender. If a Content-Type header field is not present, the recipient <em class="bcp14">MAY</em> either assume a media type of "application/octet-stream" (<a href="#RFC2046" id="rfc.xref.RFC2046.3"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types">[RFC2046]</cite></a>, <a href="http://tools.ietf.org/html/rfc2046#section-4.5.1">Section 4.5.1</a>) or examine the data to determine its type.
     969                  </p>
     970                  <p id="rfc.section.3.1.1.5.p.6">In practice, resource owners do not always properly configure their origin server to provide the correct Content-Type for
     971                     a given representation, with the result that some clients will examine a payload's content and override the specified type.
     972                     Clients that do so risk drawing incorrect conclusions, which might expose additional security risks (e.g., "privilege escalation").
     973                     Furthermore, it is impossible to determine the sender's intent by examining the data format: many data formats match multiple
     974                     media types that differ only in processing semantics. Implementers are encouraged to provide a means of disabling such "content
     975                     sniffing" when it is used.
     976                  </p>
     977               </div>
     978            </div>
     979            <div id="data.encoding">
     980               <h3 id="rfc.section.3.1.2"><a href="#rfc.section.3.1.2">3.1.2</a>&nbsp;<a href="#data.encoding">Encoding for Compression or Integrity</a></h3>
     981               <div id="content.codings">
     982                  <div id="rfc.iref.c.3"></div>
     983                  <div id="rfc.iref.c.4"></div>
     984                  <div id="rfc.iref.x.1"></div>
     985                  <div id="rfc.iref.d.1"></div>
     986                  <div id="rfc.iref.g.7"></div>
     987                  <div id="rfc.iref.x.2"></div>
     988                  <h4 id="rfc.section.3.1.2.1"><a href="#rfc.section.3.1.2.1">3.1.2.1</a>&nbsp;<a href="#content.codings">Content Codings</a></h4>
     989                  <p id="rfc.section.3.1.2.1.p.1">Content coding values indicate an encoding transformation that has been or can be applied to a representation. Content codings
     990                     are primarily used to allow a representation to be compressed or otherwise usefully transformed without losing the identity
     991                     of its underlying media type and without loss of information. Frequently, the representation is stored in coded form, transmitted
     992                     directly, and only decoded by the final recipient.
     993                  </p>
     994                  <div id="rfc.figure.u.7"></div><pre class="inline"><span id="rfc.iref.g.8"></span>  <a href="#content.codings" class="smpl">content-coding</a>   = <a href="#imported.abnf" class="smpl">token</a>
     995</pre><p id="rfc.section.3.1.2.1.p.3">All content-coding values are case-insensitive and ought to be registered within the "HTTP Content Coding Registry", as defined
     996                     in <a href="#content.coding.registry" title="Content Coding Registry">Section&nbsp;8.4</a>. They are used in the <a href="#header.accept-encoding" class="smpl">Accept-Encoding</a> (<a href="#header.accept-encoding" id="rfc.xref.header.accept-encoding.1" title="Accept-Encoding">Section&nbsp;5.3.4</a>) and <a href="#header.content-encoding" class="smpl">Content-Encoding</a> (<a href="#header.content-encoding" id="rfc.xref.header.content-encoding.2" title="Content-Encoding">Section&nbsp;3.1.2.2</a>) header fields.
     997                  </p>
     998                  <p id="rfc.section.3.1.2.1.p.4">The following content-coding values are defined by this specification: </p>
     999                  <ul class="empty">
     1000                     <li>compress (and x-compress): See <a href="p1-messaging.html#compress.coding" title="Compress Coding">Section 4.2.1</a> of <a href="#RFC7230" id="rfc.xref.RFC7230.7"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>.
     1001                     </li>
     1002                     <li>deflate: See <a href="p1-messaging.html#deflate.coding" title="Deflate Coding">Section 4.2.2</a> of <a href="#RFC7230" id="rfc.xref.RFC7230.8"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>.
     1003                     </li>
     1004                     <li>gzip (and x-gzip): See <a href="p1-messaging.html#gzip.coding" title="Gzip Coding">Section 4.2.3</a> of <a href="#RFC7230" id="rfc.xref.RFC7230.9"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>.
     1005                     </li>
     1006                  </ul>
     1007               </div>
     1008               <div id="header.content-encoding">
     1009                  <div id="rfc.iref.c.5"></div>
     1010                  <h4 id="rfc.section.3.1.2.2"><a href="#rfc.section.3.1.2.2">3.1.2.2</a>&nbsp;<a href="#header.content-encoding">Content-Encoding</a></h4>
     1011                  <p id="rfc.section.3.1.2.2.p.1">The "Content-Encoding" header field indicates what content codings have been applied to the representation, beyond those inherent
     1012                     in the media type, and thus what decoding mechanisms have to be applied in order to obtain data in the media type referenced
     1013                     by the <a href="#header.content-type" class="smpl">Content-Type</a> header field. Content-Encoding is primarily used to allow a representation's data to be compressed without losing the identity
     1014                     of its underlying media type.
     1015                  </p>
     1016                  <div id="rfc.figure.u.8"></div><pre class="inline"><span id="rfc.iref.g.9"></span>  <a href="#header.content-encoding" class="smpl">Content-Encoding</a> = 1#<a href="#content.codings" class="smpl">content-coding</a>
     1017</pre><p id="rfc.section.3.1.2.2.p.3">An example of its use is</p>
     1018                  <div id="rfc.figure.u.9"></div><pre class="text">  Content-Encoding: gzip
     1019</pre><p id="rfc.section.3.1.2.2.p.5">If one or more encodings have been applied to a representation, the sender that applied the encodings <em class="bcp14">MUST</em> generate a Content-Encoding header field that lists the content codings in the order in which they were applied. Additional
     1020                     information about the encoding parameters can be provided by other header fields not defined by this specification.
     1021                  </p>
     1022                  <p id="rfc.section.3.1.2.2.p.6">Unlike Transfer-Encoding (<a href="p1-messaging.html#header.transfer-encoding" title="Transfer-Encoding">Section 3.3.1</a> of <a href="#RFC7230" id="rfc.xref.RFC7230.10"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>), the codings listed in Content-Encoding are a characteristic of the representation; the representation is defined in terms
     1023                     of the coded form, and all other metadata about the representation is about the coded form unless otherwise noted in the metadata
     1024                     definition. Typically, the representation is only decoded just prior to rendering or analogous usage.
     1025                  </p>
     1026                  <p id="rfc.section.3.1.2.2.p.7">If the media type includes an inherent encoding, such as a data format that is always compressed, then that encoding would
     1027                     not be restated in Content-Encoding even if it happens to be the same algorithm as one of the content codings. Such a content
     1028                     coding would only be listed if, for some bizarre reason, it is applied a second time to form the representation. Likewise,
     1029                     an origin server might choose to publish the same data as multiple representations that differ only in whether the coding
     1030                     is defined as part of <a href="#header.content-type" class="smpl">Content-Type</a> or Content-Encoding, since some user agents will behave differently in their handling of each response (e.g., open a "Save
     1031                     as ..." dialog instead of automatic decompression and rendering of content).
     1032                  </p>
     1033                  <p id="rfc.section.3.1.2.2.p.8">An origin server <em class="bcp14">MAY</em> respond with a status code of <a href="#status.415" class="smpl">415 (Unsupported Media Type)</a> if a representation in the request message has a content coding that is not acceptable.
     1034                  </p>
     1035               </div>
     1036            </div>
     1037            <div id="audience.language">
     1038               <h3 id="rfc.section.3.1.3"><a href="#rfc.section.3.1.3">3.1.3</a>&nbsp;<a href="#audience.language">Audience Language</a></h3>
     1039               <div id="language.tags">
     1040                  <h4 id="rfc.section.3.1.3.1"><a href="#rfc.section.3.1.3.1">3.1.3.1</a>&nbsp;<a href="#language.tags">Language Tags</a></h4>
     1041                  <p id="rfc.section.3.1.3.1.p.1">A language tag, as defined in <a href="#RFC5646" id="rfc.xref.RFC5646.1"><cite title="Tags for Identifying Languages">[RFC5646]</cite></a>, identifies a natural language spoken, written, or otherwise conveyed by human beings for communication of information to
     1042                     other human beings. Computer languages are explicitly excluded.
     1043                  </p>
     1044                  <p id="rfc.section.3.1.3.1.p.2">HTTP uses language tags within the <a href="#header.accept-language" class="smpl">Accept-Language</a> and <a href="#header.content-language" class="smpl">Content-Language</a> header fields. <a href="#header.accept-language" class="smpl">Accept-Language</a> uses the broader language-range production defined in <a href="#header.accept-language" id="rfc.xref.header.accept-language.1" title="Accept-Language">Section&nbsp;5.3.5</a>, whereas <a href="#header.content-language" class="smpl">Content-Language</a> uses the language-tag production defined below.
     1045                  </p>
     1046                  <div id="rfc.figure.u.10"></div><pre class="inline"><span id="rfc.iref.g.10"></span>  <a href="#language.tags" class="smpl">language-tag</a> = &lt;Language-Tag, defined in <a href="#RFC5646" id="rfc.xref.RFC5646.2"><cite title="Tags for Identifying Languages">[RFC5646]</cite></a>, <a href="http://tools.ietf.org/html/rfc5646#section-2.1">Section 2.1</a>&gt;
     1047</pre><p id="rfc.section.3.1.3.1.p.4">A language tag is a sequence of one or more case-insensitive subtags, each separated by a hyphen character ("-", %x2D). In
     1048                     most cases, a language tag consists of a primary language subtag that identifies a broad family of related languages (e.g.,
     1049                     "en" = English), which is optionally followed by a series of subtags that refine or narrow that language's range (e.g., "en-CA"
     1050                     = the variety of English as communicated in Canada). Whitespace is not allowed within a language tag. Example tags include:
     1051                  </p>
     1052                  <div id="rfc.figure.u.11"></div><pre class="text">  fr, en-US, es-419, az-Arab, x-pig-latin, man-Nkoo-GN
     1053</pre><p id="rfc.section.3.1.3.1.p.6">See <a href="#RFC5646" id="rfc.xref.RFC5646.3"><cite title="Tags for Identifying Languages">[RFC5646]</cite></a> for further information.
     1054                  </p>
     1055               </div>
     1056               <div id="header.content-language">
     1057                  <div id="rfc.iref.c.6"></div>
     1058                  <h4 id="rfc.section.3.1.3.2"><a href="#rfc.section.3.1.3.2">3.1.3.2</a>&nbsp;<a href="#header.content-language">Content-Language</a></h4>
     1059                  <p id="rfc.section.3.1.3.2.p.1">The "Content-Language" header field describes the natural language(s) of the intended audience for the representation. Note
     1060                     that this might not be equivalent to all the languages used within the representation.
     1061                  </p>
     1062                  <div id="rfc.figure.u.12"></div><pre class="inline"><span id="rfc.iref.g.11"></span>  <a href="#header.content-language" class="smpl">Content-Language</a> = 1#<a href="#language.tags" class="smpl">language-tag</a>
     1063</pre><p id="rfc.section.3.1.3.2.p.3">Language tags are defined in <a href="#language.tags" title="Language Tags">Section&nbsp;3.1.3.1</a>. The primary purpose of Content-Language is to allow a user to identify and differentiate representations according to the
     1064                     users' own preferred language. Thus, if the content is intended only for a Danish-literate audience, the appropriate field
     1065                     is
     1066                  </p>
     1067                  <div id="rfc.figure.u.13"></div><pre class="text">  Content-Language: da
     1068</pre><p id="rfc.section.3.1.3.2.p.5">If no Content-Language is specified, the default is that the content is intended for all language audiences. This might mean
     1069                     that the sender does not consider it to be specific to any natural language, or that the sender does not know for which language
     1070                     it is intended.
     1071                  </p>
     1072                  <p id="rfc.section.3.1.3.2.p.6">Multiple languages <em class="bcp14">MAY</em> be listed for content that is intended for multiple audiences. For example, a rendition of the "Treaty of Waitangi", presented
     1073                     simultaneously in the original Maori and English versions, would call for
     1074                  </p>
     1075                  <div id="rfc.figure.u.14"></div><pre class="text">  Content-Language: mi, en
     1076</pre><p id="rfc.section.3.1.3.2.p.8">However, just because multiple languages are present within a representation does not mean that it is intended for multiple
     1077                     linguistic audiences. An example would be a beginner's language primer, such as "A First Lesson in Latin", which is clearly
     1078                     intended to be used by an English-literate audience. In this case, the Content-Language would properly only include "en".
     1079                  </p>
     1080                  <p id="rfc.section.3.1.3.2.p.9">Content-Language <em class="bcp14">MAY</em> be applied to any media type — it is not limited to textual documents.
     1081                  </p>
     1082               </div>
     1083            </div>
     1084            <div id="identification">
     1085               <h3 id="rfc.section.3.1.4"><a href="#rfc.section.3.1.4">3.1.4</a>&nbsp;<a href="#identification">Identification</a></h3>
     1086               <div id="identifying.payload">
     1087                  <h4 id="rfc.section.3.1.4.1"><a href="#rfc.section.3.1.4.1">3.1.4.1</a>&nbsp;<a href="#identifying.payload">Identifying a Representation</a></h4>
     1088                  <p id="rfc.section.3.1.4.1.p.1">When a complete or partial representation is transferred in a message payload, it is often desirable for the sender to supply,
     1089                     or the recipient to determine, an identifier for a resource corresponding to that representation.
     1090                  </p>
     1091                  <p id="rfc.section.3.1.4.1.p.2">For a request message: </p>
     1092                  <ul>
     1093                     <li>If the request has a <a href="#header.content-location" class="smpl">Content-Location</a> header field, then the sender asserts that the payload is a representation of the resource identified by the Content-Location
     1094                        field-value. However, such an assertion cannot be trusted unless it can be verified by other means (not defined by this specification).
     1095                        The information might still be useful for revision history links.
     1096                     </li>
     1097                     <li>Otherwise, the payload is unidentified.</li>
     1098                  </ul>
     1099                  <p id="rfc.section.3.1.4.1.p.3">For a response message, the following rules are applied in order until a match is found: </p>
     1100                  <ol>
     1101                     <li>If the request method is GET or HEAD and the response status code is <a href="#status.200" class="smpl">200 (OK)</a>, <a href="#status.204" class="smpl">204 (No Content)</a>, <a href="p5-range.html#status.206" class="smpl">206 (Partial Content)</a>, or <a href="p4-conditional.html#status.304" class="smpl">304 (Not Modified)</a>, the payload is a representation of the resource identified by the effective request URI (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 5.5</a> of <a href="#RFC7230" id="rfc.xref.RFC7230.11"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>).
     1102                     </li>
     1103                     <li>If the request method is GET or HEAD and the response status code is <a href="#status.203" class="smpl">203 (Non-Authoritative Information)</a>, the payload is a potentially modified or enhanced representation of the <a href="#resources" class="smpl">target resource</a> as provided by an intermediary.
     1104                     </li>
     1105                     <li>If the response has a <a href="#header.content-location" class="smpl">Content-Location</a> header field and its field-value is a reference to the same URI as the effective request URI, the payload is a representation
     1106                        of the resource identified by the effective request URI.
     1107                     </li>
     1108                     <li>If the response has a <a href="#header.content-location" class="smpl">Content-Location</a> header field and its field-value is a reference to a URI different from the effective request URI, then the sender asserts
     1109                        that the payload is a representation of the resource identified by the Content-Location field-value. However, such an assertion
     1110                        cannot be trusted unless it can be verified by other means (not defined by this specification).
     1111                     </li>
     1112                     <li>Otherwise, the payload is unidentified.</li>
     1113                  </ol>
     1114               </div>
     1115               <div id="header.content-location">
     1116                  <div id="rfc.iref.c.7"></div>
     1117                  <h4 id="rfc.section.3.1.4.2"><a href="#rfc.section.3.1.4.2">3.1.4.2</a>&nbsp;<a href="#header.content-location">Content-Location</a></h4>
     1118                  <p id="rfc.section.3.1.4.2.p.1">The "Content-Location" header field references a URI that can be used as an identifier for a specific resource corresponding
     1119                     to the representation in this message's payload. In other words, if one were to perform a GET request on this URI at the time
     1120                     of this message's generation, then a <a href="#status.200" class="smpl">200 (OK)</a> response would contain the same representation that is enclosed as payload in this message.
     1121                  </p>
     1122                  <div id="rfc.figure.u.15"></div><pre class="inline"><span id="rfc.iref.g.12"></span>  <a href="#header.content-location" class="smpl">Content-Location</a> = <a href="#imported.abnf" class="smpl">absolute-URI</a> / <a href="#imported.abnf" class="smpl">partial-URI</a>
     1123</pre><p id="rfc.section.3.1.4.2.p.3">The Content-Location value is not a replacement for the effective Request URI (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 5.5</a> of <a href="#RFC7230" id="rfc.xref.RFC7230.12"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>). It is representation metadata. It has the same syntax and semantics as the header field of the same name defined for MIME
     1124                     body parts in <a href="http://tools.ietf.org/html/rfc2557#section-4">Section 4</a> of <a href="#RFC2557" id="rfc.xref.RFC2557.1"><cite title="MIME Encapsulation of Aggregate Documents, such as HTML (MHTML)">[RFC2557]</cite></a>. However, its appearance in an HTTP message has some special implications for HTTP recipients.
     1125                  </p>
     1126                  <p id="rfc.section.3.1.4.2.p.4">If Content-Location is included in a <a href="#status.2xx" class="smpl">2xx (Successful)</a> response message and its value refers (after conversion to absolute form) to a URI that is the same as the effective request
     1127                     URI, then the recipient <em class="bcp14">MAY</em> consider the payload to be a current representation of that resource at the time indicated by the message origination date.
     1128                     For a GET (<a href="#GET" id="rfc.xref.GET.2" title="GET">Section&nbsp;4.3.1</a>) or HEAD (<a href="#HEAD" id="rfc.xref.HEAD.1" title="HEAD">Section&nbsp;4.3.2</a>) request, this is the same as the default semantics when no Content-Location is provided by the server. For a state-changing
     1129                     request like PUT (<a href="#PUT" id="rfc.xref.PUT.1" title="PUT">Section&nbsp;4.3.4</a>) or POST (<a href="#POST" id="rfc.xref.POST.1" title="POST">Section&nbsp;4.3.3</a>), it implies that the server's response contains the new representation of that resource, thereby distinguishing it from
     1130                     representations that might only report about the action (e.g., "It worked!"). This allows authoring applications to update
     1131                     their local copies without the need for a subsequent GET request.
     1132                  </p>
     1133                  <p id="rfc.section.3.1.4.2.p.5">If Content-Location is included in a <a href="#status.2xx" class="smpl">2xx (Successful)</a> response message and its field-value refers to a URI that differs from the effective request URI, then the origin server claims
     1134                     that the URI is an identifier for a different resource corresponding to the enclosed representation. Such a claim can only
     1135                     be trusted if both identifiers share the same resource owner, which cannot be programmatically determined via HTTP.
     1136                  </p>
     1137                  <ul>
     1138                     <li>For a response to a GET or HEAD request, this is an indication that the effective request URI refers to a resource that is
     1139                        subject to content negotiation and the Content-Location field-value is a more specific identifier for the <a href="#representations" class="smpl">selected representation</a>.
     1140                     </li>
     1141                     <li>For a <a href="#status.201" class="smpl">201 (Created)</a> response to a state-changing method, a Content-Location field-value that is identical to the <a href="#header.location" class="smpl">Location</a> field-value indicates that this payload is a current representation of the newly created resource.
     1142                     </li>
     1143                     <li>Otherwise, such a Content-Location indicates that this payload is a representation reporting on the requested action's status
     1144                        and that the same report is available (for future access with GET) at the given URI. For example, a purchase transaction made
     1145                        via a POST request might include a receipt document as the payload of the <a href="#status.200" class="smpl">200 (OK)</a> response; the Content-Location field-value provides an identifier for retrieving a copy of that same receipt in the future.
     1146                     </li>
     1147                  </ul>
     1148                  <p id="rfc.section.3.1.4.2.p.6">A user agent that sends Content-Location in a request message is stating that its value refers to where the user agent originally
     1149                     obtained the content of the enclosed representation (prior to any modifications made by that user agent). In other words,
     1150                     the user agent is providing a back link to the source of the original representation.
     1151                  </p>
     1152                  <p id="rfc.section.3.1.4.2.p.7">An origin server that receives a Content-Location field in a request message <em class="bcp14">MUST</em> treat the information as transitory request context rather than as metadata to be saved verbatim as part of the representation.
     1153                     An origin server <em class="bcp14">MAY</em> use that context to guide in processing the request or to save it for other uses, such as within source links or versioning
     1154                     metadata. However, an origin server <em class="bcp14">MUST NOT</em> use such context information to alter the request semantics.
     1155                  </p>
     1156                  <p id="rfc.section.3.1.4.2.p.8">For example, if a client makes a PUT request on a negotiated resource and the origin server accepts that PUT (without redirection),
     1157                     then the new state of that resource is expected to be consistent with the one representation supplied in that PUT; the Content-Location
     1158                     cannot be used as a form of reverse content selection identifier to update only one of the negotiated representations. If
     1159                     the user agent had wanted the latter semantics, it would have applied the PUT directly to the Content-Location URI.
     1160                  </p>
     1161               </div>
     1162            </div>
     1163         </div>
     1164         <div id="representation.data">
     1165            <h2 id="rfc.section.3.2"><a href="#rfc.section.3.2">3.2</a>&nbsp;<a href="#representation.data">Representation Data</a></h2>
     1166            <p id="rfc.section.3.2.p.1">The representation data associated with an HTTP message is either provided as the payload body of the message or referred
     1167               to by the message semantics and the effective request URI. The representation data is in a format and encoding defined by
     1168               the representation metadata header fields.
     1169            </p>
     1170            <p id="rfc.section.3.2.p.2">The data type of the representation data is determined via the header fields <a href="#header.content-type" class="smpl">Content-Type</a> and <a href="#header.content-encoding" class="smpl">Content-Encoding</a>. These define a two-layer, ordered encoding model:
     1171            </p>
     1172            <div id="rfc.figure.u.16"></div><pre class="text">  representation-data := Content-Encoding( Content-Type( bits ) )
     1173</pre></div>
     1174         <div id="payload">
     1175            <div id="rfc.iref.p.1"></div>
     1176            <h2 id="rfc.section.3.3"><a href="#rfc.section.3.3">3.3</a>&nbsp;<a href="#payload">Payload Semantics</a></h2>
     1177            <p id="rfc.section.3.3.p.1">Some HTTP messages transfer a complete or partial representation as the message "<dfn>payload</dfn>". In some cases, a payload might contain only the associated representation's header fields (e.g., responses to HEAD) or
     1178               only some part(s) of the representation data (e.g., the <a href="p5-range.html#status.206" class="smpl">206 (Partial Content)</a> status code).
     1179            </p>
     1180            <p id="rfc.section.3.3.p.2">The purpose of a payload in a request is defined by the method semantics. For example, a representation in the payload of
     1181               a PUT request (<a href="#PUT" id="rfc.xref.PUT.2" title="PUT">Section&nbsp;4.3.4</a>) represents the desired state of the <a href="#resources" class="smpl">target resource</a> if the request is successfully applied, whereas a representation in the payload of a POST request (<a href="#POST" id="rfc.xref.POST.2" title="POST">Section&nbsp;4.3.3</a>) represents information to be processed by the target resource.
     1182            </p>
     1183            <p id="rfc.section.3.3.p.3">In a response, the payload's purpose is defined by both the request method and the response status code. For example, the
     1184               payload of a <a href="#status.200" class="smpl">200 (OK)</a> response to GET (<a href="#GET" id="rfc.xref.GET.3" title="GET">Section&nbsp;4.3.1</a>) represents the current state of the <a href="#resources" class="smpl">target resource</a>, as observed at the time of the message origination date (<a href="#header.date" id="rfc.xref.header.date.1" title="Date">Section&nbsp;7.1.1.2</a>), whereas the payload of the same status code in a response to POST might represent either the processing result or the new
     1185               state of the target resource after applying the processing. Response messages with an error status code usually contain a
     1186               payload that represents the error condition, such that it describes the error state and what next steps are suggested for
     1187               resolving it.
     1188            </p>
     1189            <p id="rfc.section.3.3.p.4">Header fields that specifically describe the payload, rather than the associated representation, are referred to as "payload
     1190               header fields". Payload header fields are defined in other parts of this specification, due to their impact on message parsing.
     1191            </p>
     1192            <div id="rfc.table.u.2">
     1193               <table class="tt full left" cellpadding="3" cellspacing="0">
     1194                  <thead>
     1195                     <tr>
     1196                        <th>Header Field Name</th>
     1197                        <th>Defined in...</th>
     1198                     </tr>
     1199                  </thead>
     1200                  <tbody>
     1201                     <tr>
     1202                        <td class="left">Content-Length</td>
     1203                        <td class="left"><a href="p1-messaging.html#header.content-length" title="Content-Length">Section 3.3.2</a> of <a href="#RFC7230" id="rfc.xref.RFC7230.13"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a></td>
     1204                     </tr>
     1205                     <tr>
     1206                        <td class="left">Content-Range</td>
     1207                        <td class="left"><a href="p5-range.html#header.content-range" title="Content-Range">Section 4.2</a> of <a href="#RFC7233" id="rfc.xref.RFC7233.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Range Requests">[RFC7233]</cite></a></td>
     1208                     </tr>
     1209                     <tr>
     1210                        <td class="left">Trailer</td>
     1211                        <td class="left"><a href="p1-messaging.html#header.trailer" title="Trailer">Section 4.4</a> of <a href="#RFC7230" id="rfc.xref.RFC7230.14"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a></td>
     1212                     </tr>
     1213                     <tr>
     1214                        <td class="left">Transfer-Encoding</td>
     1215                        <td class="left"><a href="p1-messaging.html#header.transfer-encoding" title="Transfer-Encoding">Section 3.3.1</a> of <a href="#RFC7230" id="rfc.xref.RFC7230.15"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a></td>
     1216                     </tr>
     1217                  </tbody>
     1218               </table>
     1219            </div>
     1220         </div>
     1221         <div id="content.negotiation">
     1222            <h2 id="rfc.section.3.4"><a href="#rfc.section.3.4">3.4</a>&nbsp;<a href="#content.negotiation">Content Negotiation</a></h2>
     1223            <p id="rfc.section.3.4.p.1">When responses convey payload information, whether indicating a success or an error, the origin server often has different
     1224               ways of representing that information; for example, in different formats, languages, or encodings. Likewise, different users
     1225               or user agents might have differing capabilities, characteristics, or preferences that could influence which representation,
     1226               among those available, would be best to deliver. For this reason, HTTP provides mechanisms for <a href="#content.negotiation" class="smpl">content negotiation</a>.
     1227            </p>
     1228            <p id="rfc.section.3.4.p.2">This specification defines two patterns of content negotiation that can be made visible within the protocol: "proactive",
     1229               where the server selects the representation based upon the user agent's stated preferences, and "reactive" negotiation, where
     1230               the server provides a list of representations for the user agent to choose from. Other patterns of content negotiation include
     1231               "conditional content", where the representation consists of multiple parts that are selectively rendered based on user agent
     1232               parameters, "active content", where the representation contains a script that makes additional (more specific) requests based
     1233               on the user agent characteristics, and "Transparent Content Negotiation" (<a href="#RFC2295" id="rfc.xref.RFC2295.1"><cite title="Transparent Content Negotiation in HTTP">[RFC2295]</cite></a>), where content selection is performed by an intermediary. These patterns are not mutually exclusive, and each has trade-offs
     1234               in applicability and practicality.
     1235            </p>
     1236            <p id="rfc.section.3.4.p.3">Note that, in all cases, HTTP is not aware of the resource semantics. The consistency with which an origin server responds
     1237               to requests, over time and over the varying dimensions of content negotiation, and thus the "sameness" of a resource's observed
     1238               representations over time, is determined entirely by whatever entity or algorithm selects or generates those responses. HTTP
     1239               pays no attention to the man behind the curtain.
     1240            </p>
     1241            <div id="proactive.negotiation">
     1242               <h3 id="rfc.section.3.4.1"><a href="#rfc.section.3.4.1">3.4.1</a>&nbsp;<a href="#proactive.negotiation">Proactive Negotiation</a></h3>
     1243               <p id="rfc.section.3.4.1.p.1">When content negotiation preferences are sent by the user agent in a request to encourage an algorithm located at the server
     1244                  to select the preferred representation, it is called <dfn>proactive negotiation</dfn> (a.k.a., <dfn>server-driven negotiation</dfn>). Selection is based on the available representations for a response (the dimensions over which it might vary, such as language,
     1245                  content-coding, etc.) compared to various information supplied in the request, including both the explicit negotiation fields
     1246                  of <a href="#request.conneg" title="Content Negotiation">Section&nbsp;5.3</a> and implicit characteristics, such as the client's network address or parts of the <a href="#header.user-agent" class="smpl">User-Agent</a> field.
     1247               </p>
     1248               <p id="rfc.section.3.4.1.p.2">Proactive negotiation is advantageous when the algorithm for selecting from among the available representations is difficult
     1249                  to describe to a user agent, or when the server desires to send its "best guess" to the user agent along with the first response
     1250                  (hoping to avoid the round trip delay of a subsequent request if the "best guess" is good enough for the user). In order to
     1251                  improve the server's guess, a user agent <em class="bcp14">MAY</em> send request header fields that describe its preferences.
     1252               </p>
     1253               <p id="rfc.section.3.4.1.p.3">Proactive negotiation has serious disadvantages: </p>
     1254               <ul>
     1255                  <li>It is impossible for the server to accurately determine what might be "best" for any given user, since that would require
     1256                     complete knowledge of both the capabilities of the user agent and the intended use for the response (e.g., does the user want
     1257                     to view it on screen or print it on paper?);
     1258                  </li>
     1259                  <li>Having the user agent describe its capabilities in every request can be both very inefficient (given that only a small percentage
     1260                     of responses have multiple representations) and a potential risk to the user's privacy;
     1261                  </li>
     1262                  <li>It complicates the implementation of an origin server and the algorithms for generating responses to a request; and,</li>
     1263                  <li>It limits the reusability of responses for shared caching.</li>
     1264               </ul>
     1265               <p id="rfc.section.3.4.1.p.4">A user agent cannot rely on proactive negotiation preferences being consistently honored, since the origin server might not
     1266                  implement proactive negotiation for the requested resource or might decide that sending a response that doesn't conform to
     1267                  the user agent's preferences is better than sending a <a href="#status.406" class="smpl">406 (Not Acceptable)</a> response.
     1268               </p>
     1269               <p id="rfc.section.3.4.1.p.5">A <a href="#header.vary" class="smpl">Vary</a> header field (<a href="#header.vary" id="rfc.xref.header.vary.1" title="Vary">Section&nbsp;7.1.4</a>) is often sent in a response subject to proactive negotiation to indicate what parts of the request information were used
     1270                  in the selection algorithm.
     1271               </p>
     1272            </div>
     1273            <div id="reactive.negotiation">
     1274               <h3 id="rfc.section.3.4.2"><a href="#rfc.section.3.4.2">3.4.2</a>&nbsp;<a href="#reactive.negotiation">Reactive Negotiation</a></h3>
     1275               <p id="rfc.section.3.4.2.p.1">With <dfn>reactive negotiation</dfn> (a.k.a., <dfn>agent-driven negotiation</dfn>), selection of the best response representation (regardless of the status code) is performed by the user agent after receiving
     1276                  an initial response from the origin server that contains a list of resources for alternative representations. If the user
     1277                  agent is not satisfied by the initial response representation, it can perform a GET request on one or more of the alternative
     1278                  resources, selected based on metadata included in the list, to obtain a different form of representation for that response.
     1279                  Selection of alternatives might be performed automatically by the user agent or manually by the user selecting from a generated
     1280                  (possibly hypertext) menu.
     1281               </p>
     1282               <p id="rfc.section.3.4.2.p.2">Note that the above refers to representations of the response, in general, not representations of the resource. The alternative
     1283                  representations are only considered representations of the target resource if the response in which those alternatives are
     1284                  provided has the semantics of being a representation of the target resource (e.g., a <a href="#status.200" class="smpl">200 (OK)</a> response to a GET request) or has the semantics of providing links to alternative representations for the target resource
     1285                  (e.g., a <a href="#status.300" class="smpl">300 (Multiple Choices)</a> response to a GET request).
     1286               </p>
     1287               <p id="rfc.section.3.4.2.p.3">A server might choose not to send an initial representation, other than the list of alternatives, and thereby indicate that
     1288                  reactive negotiation by the user agent is preferred. For example, the alternatives listed in responses with the <a href="#status.300" class="smpl">300 (Multiple Choices)</a> and <a href="#status.406" class="smpl">406 (Not Acceptable)</a> status codes include information about the available representations so that the user or user agent can react by making a
     1289                  selection.
     1290               </p>
     1291               <p id="rfc.section.3.4.2.p.4">Reactive negotiation is advantageous when the response would vary over commonly used dimensions (such as type, language, or
     1292                  encoding), when the origin server is unable to determine a user agent's capabilities from examining the request, and generally
     1293                  when public caches are used to distribute server load and reduce network usage.
     1294               </p>
     1295               <p id="rfc.section.3.4.2.p.5">Reactive negotiation suffers from the disadvantages of transmitting a list of alternatives to the user agent, which degrades
     1296                  user-perceived latency if transmitted in the header section, and needing a second request to obtain an alternate representation.
     1297                  Furthermore, this specification does not define a mechanism for supporting automatic selection, though it does not prevent
     1298                  such a mechanism from being developed as an extension.
     1299               </p>
     1300            </div>
     1301         </div>
     1302      </div>
     1303      <div id="methods">
     1304         <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a>&nbsp;<a href="#methods">Request Methods</a></h1>
     1305         <div id="method.overview">
     1306            <h2 id="rfc.section.4.1"><a href="#rfc.section.4.1">4.1</a>&nbsp;<a href="#method.overview">Overview</a></h2>
     1307            <p id="rfc.section.4.1.p.1">The request method token is the primary source of request semantics; it indicates the purpose for which the client has made
     1308               this request and what is expected by the client as a successful result.
     1309            </p>
     1310            <p id="rfc.section.4.1.p.2">The request method's semantics might be further specialized by the semantics of some header fields when present in a request
     1311               (<a href="#request.header.fields" title="Request Header Fields">Section&nbsp;5</a>) if those additional semantics do not conflict with the method. For example, a client can send conditional request header
     1312               fields (<a href="#request.conditionals" title="Conditionals">Section&nbsp;5.2</a>) to make the requested action conditional on the current state of the target resource (<a href="#RFC7232" id="rfc.xref.RFC7232.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[RFC7232]</cite></a>).
     1313            </p>
     1314            <div id="rfc.figure.u.17"></div><pre class="inline"><span id="rfc.iref.g.13"></span>  <a href="#method.overview" class="smpl">method</a> = <a href="#imported.abnf" class="smpl">token</a>
     1315</pre><p id="rfc.section.4.1.p.4">HTTP was originally designed to be usable as an interface to distributed object systems. The request method was envisioned
     1316               as applying semantics to a <a href="#resources" class="smpl">target resource</a> in much the same way as invoking a defined method on an identified object would apply semantics. The method token is case-sensitive
     1317               because it might be used as a gateway to object-based systems with case-sensitive method names.
     1318            </p>
     1319            <p id="rfc.section.4.1.p.5">Unlike distributed objects, the standardized request methods in HTTP are not resource-specific, since uniform interfaces provide
     1320               for better visibility and reuse in network-based systems <a href="#REST" id="rfc.xref.REST.2"><cite title="Architectural Styles and the Design of Network-based Software Architectures">[REST]</cite></a>. Once defined, a standardized method ought to have the same semantics when applied to any resource, though each resource
     1321               determines for itself whether those semantics are implemented or allowed.
     1322            </p>
     1323            <p id="rfc.section.4.1.p.6">This specification defines a number of standardized methods that are commonly used in HTTP, as outlined by the following table.
     1324               By convention, standardized methods are defined in all-uppercase US-ASCII letters.
     1325            </p>
     1326            <div id="rfc.table.1">
     1327               <div id="table.of.methods"></div>
     1328               <table class="tt full left" cellpadding="3" cellspacing="0">
     1329                  <thead>
     1330                     <tr>
     1331                        <th>Method</th>
     1332                        <th>Description</th>
     1333                        <th>Sec.</th>
     1334                     </tr>
     1335                  </thead>
     1336                  <tbody>
     1337                     <tr>
     1338                        <td class="left">GET</td>
     1339                        <td class="left">Transfer a current representation of the target resource.</td>
     1340                        <td class="left"><a href="#GET" id="rfc.xref.GET.4" title="GET">4.3.1</a></td>
     1341                     </tr>
     1342                     <tr>
     1343                        <td class="left">HEAD</td>
     1344                        <td class="left">Same as GET, but only transfer the status line and header section.</td>
     1345                        <td class="left"><a href="#HEAD" id="rfc.xref.HEAD.2" title="HEAD">4.3.2</a></td>
     1346                     </tr>
     1347                     <tr>
     1348                        <td class="left">POST</td>
     1349                        <td class="left">Perform resource-specific processing on the request payload.</td>
     1350                        <td class="left"><a href="#POST" id="rfc.xref.POST.3" title="POST">4.3.3</a></td>
     1351                     </tr>
     1352                     <tr>
     1353                        <td class="left">PUT</td>
     1354                        <td class="left">Replace all current representations of the target resource with the request payload.</td>
     1355                        <td class="left"><a href="#PUT" id="rfc.xref.PUT.3" title="PUT">4.3.4</a></td>
     1356                     </tr>
     1357                     <tr>
     1358                        <td class="left">DELETE</td>
     1359                        <td class="left">Remove all current representations of the target resource.</td>
     1360                        <td class="left"><a href="#DELETE" id="rfc.xref.DELETE.1" title="DELETE">4.3.5</a></td>
     1361                     </tr>
     1362                     <tr>
     1363                        <td class="left">CONNECT</td>
     1364                        <td class="left">Establish a tunnel to the server identified by the target resource.</td>
     1365                        <td class="left"><a href="#CONNECT" id="rfc.xref.CONNECT.1" title="CONNECT">4.3.6</a></td>
     1366                     </tr>
     1367                     <tr>
     1368                        <td class="left">OPTIONS</td>
     1369                        <td class="left">Describe the communication options for the target resource.</td>
     1370                        <td class="left"><a href="#OPTIONS" id="rfc.xref.OPTIONS.1" title="OPTIONS">4.3.7</a></td>
     1371                     </tr>
     1372                     <tr>
     1373                        <td class="left">TRACE</td>
     1374                        <td class="left">Perform a message loop-back test along the path to the target resource.</td>
     1375                        <td class="left"><a href="#TRACE" id="rfc.xref.TRACE.1" title="TRACE">4.3.8</a></td>
     1376                     </tr>
     1377                  </tbody>
     1378               </table>
     1379            </div>
     1380            <p id="rfc.section.4.1.p.7">All general-purpose servers <em class="bcp14">MUST</em> support the methods GET and HEAD. All other methods are <em class="bcp14">OPTIONAL</em>.
     1381            </p>
     1382            <p id="rfc.section.4.1.p.8">Additional methods, outside the scope of this specification, have been standardized for use in HTTP. All such methods ought
     1383               to be registered within the "Hypertext Transfer Protocol (HTTP) Method Registry" maintained by IANA, as defined in <a href="#method.registry" title="Method Registry">Section&nbsp;8.1</a>.
     1384            </p>
     1385            <p id="rfc.section.4.1.p.9">The set of methods allowed by a target resource can be listed in an <a href="#header.allow" class="smpl">Allow</a> header field (<a href="#header.allow" id="rfc.xref.header.allow.1" title="Allow">Section&nbsp;7.4.1</a>). However, the set of allowed methods can change dynamically. When a request method is received that is unrecognized or not
     1386               implemented by an origin server, the origin server <em class="bcp14">SHOULD</em> respond with the <a href="#status.501" class="smpl">501 (Not Implemented)</a> status code. When a request method is received that is known by an origin server but not allowed for the target resource,
     1387               the origin server <em class="bcp14">SHOULD</em> respond with the <a href="#status.405" class="smpl">405 (Method Not Allowed)</a> status code.
     1388            </p>
     1389         </div>
     1390         <div id="method.properties">
     1391            <h2 id="rfc.section.4.2"><a href="#rfc.section.4.2">4.2</a>&nbsp;<a href="#method.properties">Common Method Properties</a></h2>
     1392            <div id="safe.methods">
     1393               <div id="rfc.iref.s.2"></div>
     1394               <h3 id="rfc.section.4.2.1"><a href="#rfc.section.4.2.1">4.2.1</a>&nbsp;<a href="#safe.methods">Safe Methods</a></h3>
     1395               <p id="rfc.section.4.2.1.p.1">Request methods are considered "<dfn>safe</dfn>" if their defined semantics are essentially read-only; i.e., the client does not request, and does not expect, any state
     1396                  change on the origin server as a result of applying a safe method to a target resource. Likewise, reasonable use of a safe
     1397                  method is not expected to cause any harm, loss of property, or unusual burden on the origin server.
     1398               </p>
     1399               <p id="rfc.section.4.2.1.p.2">This definition of safe methods does not prevent an implementation from including behavior that is potentially harmful, that
     1400                  is not entirely read-only, or that causes side effects while invoking a safe method. What is important, however, is that the
     1401                  client did not request that additional behavior and cannot be held accountable for it. For example, most servers append request
     1402                  information to access log files at the completion of every response, regardless of the method, and that is considered safe
     1403                  even though the log storage might become full and crash the server. Likewise, a safe request initiated by selecting an advertisement
     1404                  on the Web will often have the side effect of charging an advertising account.
     1405               </p>
     1406               <p id="rfc.section.4.2.1.p.3">Of the request methods defined by this specification, the GET, HEAD, OPTIONS, and TRACE methods are defined to be safe.</p>
     1407               <p id="rfc.section.4.2.1.p.4">The purpose of distinguishing between safe and unsafe methods is to allow automated retrieval processes (spiders) and cache
     1408                  performance optimization (pre-fetching) to work without fear of causing harm. In addition, it allows a user agent to apply
     1409                  appropriate constraints on the automated use of unsafe methods when processing potentially untrusted content.
     1410               </p>
     1411               <p id="rfc.section.4.2.1.p.5">A user agent <em class="bcp14">SHOULD</em> distinguish between safe and unsafe methods when presenting potential actions to a user, such that the user can be made aware
     1412                  of an unsafe action before it is requested.
     1413               </p>
     1414               <p id="rfc.section.4.2.1.p.6">When a resource is constructed such that parameters within the effective request URI have the effect of selecting an action,
     1415                  it is the resource owner's responsibility to ensure that the action is consistent with the request method semantics. For example,
     1416                  it is common for Web-based content editing software to use actions within query parameters, such as "page?do=delete". If the
     1417                  purpose of such a resource is to perform an unsafe action, then the resource owner <em class="bcp14">MUST</em> disable or disallow that action when it is accessed using a safe request method. Failure to do so will result in unfortunate
     1418                  side effects when automated processes perform a GET on every URI reference for the sake of link maintenance, pre-fetching,
     1419                  building a search index, etc.
     1420               </p>
     1421            </div>
     1422            <div id="idempotent.methods">
     1423               <div id="rfc.iref.i.1"></div>
     1424               <h3 id="rfc.section.4.2.2"><a href="#rfc.section.4.2.2">4.2.2</a>&nbsp;<a href="#idempotent.methods">Idempotent Methods</a></h3>
     1425               <p id="rfc.section.4.2.2.p.1">A request method is considered "<dfn id="idempotent">idempotent</dfn>" if the intended effect on the server of multiple identical requests with that method is the same as the effect for a single
     1426                  such request. Of the request methods defined by this specification, PUT, DELETE, and safe request methods are idempotent.
     1427               </p>
     1428               <p id="rfc.section.4.2.2.p.2">Like the definition of safe, the idempotent property only applies to what has been requested by the user; a server is free
     1429                  to log each request separately, retain a revision control history, or implement other non-idempotent side effects for each
     1430                  idempotent request.
     1431               </p>
     1432               <p id="rfc.section.4.2.2.p.3">Idempotent methods are distinguished because the request can be repeated automatically if a communication failure occurs before
     1433                  the client is able to read the server's response. For example, if a client sends a PUT request and the underlying connection
     1434                  is closed before any response is received, then the client can establish a new connection and retry the idempotent request.
     1435                  It knows that repeating the request will have the same intended effect, even if the original request succeeded, though the
     1436                  response might differ.
     1437               </p>
     1438            </div>
     1439            <div id="cacheable.methods">
     1440               <div id="rfc.iref.c.8"></div>
     1441               <h3 id="rfc.section.4.2.3"><a href="#rfc.section.4.2.3">4.2.3</a>&nbsp;<a href="#cacheable.methods">Cacheable Methods</a></h3>
     1442               <p id="rfc.section.4.2.3.p.1">Request methods can be defined as "<dfn id="cacheable">cacheable</dfn>" to indicate that responses to them are allowed to be stored for future reuse; for specific requirements see <a href="#RFC7234" id="rfc.xref.RFC7234.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[RFC7234]</cite></a>. In general, safe methods that do not depend on a current or authoritative response are defined as cacheable; this specification
     1443                  defines GET, HEAD, and POST as cacheable, although the overwhelming majority of cache implementations only support GET and
     1444                  HEAD.
     1445               </p>
     1446            </div>
     1447         </div>
     1448         <div id="method.definitions">
     1449            <h2 id="rfc.section.4.3"><a href="#rfc.section.4.3">4.3</a>&nbsp;<a href="#method.definitions">Method Definitions</a></h2>
     1450            <div id="GET">
     1451               <h3 id="rfc.section.4.3.1"><a href="#rfc.section.4.3.1">4.3.1</a>&nbsp;<a href="#GET">GET</a></h3>
     1452               <div id="rfc.iref.g.14"></div>
     1453               <p id="rfc.section.4.3.1.p.1">The GET method requests transfer of a current selected representation for the <a href="#resources" class="smpl">target resource</a>. GET is the primary mechanism of information retrieval and the focus of almost all performance optimizations. Hence, when
     1454                  people speak of retrieving some identifiable information via HTTP, they are generally referring to making a GET request.
     1455               </p>
     1456               <p id="rfc.section.4.3.1.p.2">It is tempting to think of resource identifiers as remote file system pathnames and of representations as being a copy of
     1457                  the contents of such files. In fact, that is how many resources are implemented (see <a href="#attack.pathname" title="Attacks Based on File and Path Names">Section&nbsp;9.1</a> for related security considerations). However, there are no such limitations in practice. The HTTP interface for a resource
     1458                  is just as likely to be implemented as a tree of content objects, a programmatic view on various database records, or a gateway
     1459                  to other information systems. Even when the URI mapping mechanism is tied to a file system, an origin server might be configured
     1460