- From: David I. Lehn <dil@lehn.org>
- Date: Tue, 16 Jun 2015 20:23:22 -0400
- To: Melvin Carvalho <melvincarvalho@gmail.com>
- Cc: Web Payments <public-webpayments@w3.org>
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? -dave
Received on Wednesday, 17 June 2015 00:24:12 UTC