Websites aren't required to provide you content for free, and (for the most part... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

		danShumway on Jan 6, 2020 \| parent \| context \| favorite \| on: U.S. retailers rush to comply with CCPA Websites aren't required to provide you content for free, and (for the most part) shouldn't be. But they also shouldn't be able to claim that there's an implicit acceptance of TOS by visiting the site. If they want to make it a cost of accessing the site, they should put the equivalent of a paywall in front of the site for data. If I make an unauthenticated HTTP GET request to a server, and it responds with a 200, it can't claim after the fact that receiving that request means I agreed to something.

sgslo on Jan 6, 2020 [–]

There is an HTTP status code of '402' with message 'Payment Required'. Sounds like an appropriate use case for this scenario.

[1] https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/402

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact