Re: HTTP 402 (payment required) -- the missing link

On Tue, Jun 16, 2015 at 8:34 PM, Melvin Carvalho
<melvincarvalho@gmail.com> wrote:
> On 17 June 2015 at 02:23, David I. Lehn <dil@lehn.org> wrote:
>> On Tue, Jun 16, 2015 at 7:57 PM, Melvin Carvalho
>> <melvincarvalho@gmail.com> wrote:
>> > I've implemented HTTP 402 a few times for payment protected resources.
>> > ...
>> > If payment is required, how does the client know what to do next?
>> > ...
>> > What about sending a Location: header telling the client where to go
>> > next?
>> >
>> > Then the client can find all the information about how to pay, their
>> > balance, the cost etc.
>> > ...
>>
>> Won't user agents only follow that Location for 3xx codes?  How about
>> just including human and/or machine readable info in the 402 response
>> content?
>
> Seems possible.  But are you allows to return data with a 4xx?  Im not sure
> on this ...
>

Sure.  For example see all the fancy 404 HTML pages out there.  You
could also do content negotiation and return machine readable data
when appropriate.

-dave

Received on Wednesday, 17 June 2015 17:46:13 UTC