You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If request to the url returned HTTP 403 Forbidden, it will raise HttpRequestException exception. The exception object will contains a .StatusCude property but the value will be (null), and the .Message property will contains Cannot GET resource <URL>. StatusCode: Forbidden. That's not what I expected.
The text was updated successfully, but these errors were encountered:
However, maybe we should change the way we handle fail cases, given that a few people are surprised by our current approach. For instance, we could catch all exceptions and add some message to Article to indicate a failure in retrieving the article. What do you suggest? What would you want to happen instead of throwing an exception?
For this code:
If request to the url returned
HTTP 403 Forbidden
, it will raiseHttpRequestException
exception. The exception object will contains a.StatusCude
property but the value will be(null)
, and the.Message
property will containsCannot GET resource <URL>. StatusCode: Forbidden
. That's not what I expected.The text was updated successfully, but these errors were encountered: