|
|
|
|
|
by Veratyr
3109 days ago
|
|
> When you make an HTTP request, you're accessing a piece of private property. The owner of that property has every right to decide not to let you do so. It can do exactly that. It can respond with an error code or start dropping packets entirely. As far as I'm aware, LinkedIn didn't do that. Any access to LinkedIn's data requires that LinkedIn send it in a response. If LinkedIn is sending it in a response, LinkedIn can't claim that it's not authorized. |
|