60
donuts
8y

Actually sometimes the browser does make a difference...

Was getting a 500 error when using WebClient but HTTPWebRequest didn't have any issues.

Comments
  • 3
    Technically its still a server issue, as it is probably the server choking on how the 2 different options send their requests
  • 1
    @liammartens well in my case, it works in regular browsers and scraping a site isn't exactly something they expect users to do...
  • 3
    100% it is the crappy code running on the server. The logs will tell you
  • 0
    It could even be the way the agent identifies itself in the request, some servers have different handling for specific agents.. That said, the fix is generally done server-side anyway. :/
  • 0
    Just check the logs. Back end dev should know this... But i still enjoy the regular coding wars between backend and front end
Add Comment