3 ms·

The RFC offers no reasoning for this besides > The 402 (Payment Required) status code is reserved for future use. Isn't this obviously domain-specific and som

The RFC offers no reasoning for this besides > The 402 (Payment Required) status code is reserved for future use. Isn't this obviously domain-specific and something that should not be part of the transfer protocol?

westurner 7y ago
> The new W3C Payment Request API [4] makes it easy for browsers to offer a standard (and probably(?) already accessible) interface for the payment data entry screen, at least. https://www.w3.org/TR/payment-request/ https://www.w3.org/TR/payment-request/
- djur 7y ago
  The Payment Request API doesn't use 402 Payment Required, does it?
  - westurner 7y ago
    It really could
dharmab 7y ago
In this case "reserved for future use" means "don't use this for new proposals, because we already assigned it to something else that didn't pan out."
lwb 7y ago
> transfer protocol Not to be "that guy" but HTTP is an application protocol, not a transfer protocol -- this kind of thing definitely wouldn't be appropriate for TCP but it sort of makes sense for the original vision of the web.
- barbecue_sauce 7y ago
  HTTP is a transfer protocol. That’s what the second T stands for. It is also an application protocol. There is no “transfer” layer in the OSI model.
  - lwb 7y ago
    Interesting, I have only heard someone refer to "transfer protocols" as a synonym for "transport protocol". Regardless I think the point stands -- HTTP does much more than transfer, and has an opinionated model on how to deal with web resources.
bawolff 7y ago
Well an older draft version of spec says: >"The parameter to this message gives a specification of charging schemes acceptable. The client may retry the request with a suitable ChargeTo header." https://www.w3.org/Protocols/HTTP/HTRESP.html https://www.w3.org/Protocols/HTTP/HTRESP.html And charge-to is defined as >"ChargeTo: >This line if present contains account information for the costs of the application of the method requested. The format is TBS. The format of this field must be in extensible form. The first word starts with a specification of the namespace in which the account is . (This is similar to extensible URL definition.) No namespaces are currently defined. Namespaces will be registered with the registration authority . >The format of the rest of the line is a function of the charging system, but it is recommended that this include a maximum cost whose payment is authorized by the client for this transaction, and a cost unit." https://www.w3.org/Protocols/HTTP/HTRQ_Headers.html#z10 https://www.w3.org/Protocols/HTTP/HTRQ_Headers.html#z10

westurner 7y ago

> The new W3C Payment Request API [4] makes it easy for browsers to offer a standard (and probably(?) already accessible) interface for the payment data entry screen, at least. https://www.w3.org/TR/payment-request/ https://www.w3.org/TR/payment-request/

djur 7y ago
The Payment Request API doesn't use 402 Payment Required, does it?
- westurner 7y ago
  It really could

dharmab 7y ago

In this case "reserved for future use" means "don't use this for new proposals, because we already assigned it to something else that didn't pan out."

lwb 7y ago

> transfer protocol Not to be "that guy" but HTTP is an application protocol, not a transfer protocol -- this kind of thing definitely wouldn't be appropriate for TCP but it sort of makes sense for the original vision of the web.

barbecue_sauce 7y ago
HTTP is a transfer protocol. That’s what the second T stands for. It is also an application protocol. There is no “transfer” layer in the OSI model.
- lwb 7y ago
  Interesting, I have only heard someone refer to "transfer protocols" as a synonym for "transport protocol". Regardless I think the point stands -- HTTP does much more than transfer, and has an opinionated model on how to deal with web resources.

bawolff 7y ago

Well an older draft version of spec says: >"The parameter to this message gives a specification of charging schemes acceptable. The client may retry the request with a suitable ChargeTo header." https://www.w3.org/Protocols/HTTP/HTRESP.html https://www.w3.org/Protocols/HTTP/HTRESP.html And charge-to is defined as >"ChargeTo: >This line if present contains account information for the costs of the application of the method requested. The format is TBS. The format of this field must be in extensible form. The first word starts with a specification of the namespace in which the account is . (This is similar to extensible URL definition.) No namespaces are currently defined. Namespaces will be registered with the registration authority . >The format of the rest of the line is a function of the charging system, but it is recommended that this include a maximum cost whose payment is authorized by the client for this transaction, and a cost unit." https://www.w3.org/Protocols/HTTP/HTRQ_Headers.html#z10 https://www.w3.org/Protocols/HTTP/HTRQ_Headers.html#z10