4 ms·
Not really useful until there's an integrated way for paying for a piece of content. Which most people probably won't use anyway, see: http auth.
by spindritf 12y ago
Not really useful until there's an integrated way for paying for a piece of content. Which most people probably won't use anyway, see: http auth.
- michaelmior 12y agoThis gives more information than a 401 or 403, but agreed that it's use is still limited. Would make sense to return a 402 along with a redirect to a payment page.
- mhurron 12y ago> return a 402 along with a redirect So a 3xx error.
- jakio 12y agoStill useful for API's with mixed (paid & free) content, so you can keep a uniform URL structure.
- NathanKP 12y agoThis is exactly what I've used the 402 code for. Some API routes are available to all users, but others require paid access. If a freemium user attempts to access API routes behind the "paywall" I return the 402 code.
- ivoras 12y ago> Not really useful until there's an integrated way for paying for a piece of content. Bitcoins could be the solution here.