Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

9
  • 1
    $\begingroup$ That's a nice, timely hack! +1 $\endgroup$ Commented Oct 24, 2015 at 21:38
  • $\begingroup$ This worked perfectly! but I clicked bounty on the wrong person! :( $\endgroup$ Commented Oct 25, 2015 at 6:20
  • $\begingroup$ @SimonO'Doherty I have started a bounty to correct this, I just have to wait 24 hours before I can give it away. $\endgroup$ Commented Oct 25, 2015 at 11:37
  • $\begingroup$ Cheers for that. :) $\endgroup$ Commented Oct 25, 2015 at 11:38
  • 1
    $\begingroup$ @ChristopherHaydock Sorry, I posted without testing... The Wolfram HTTPClient is using expect: "100-continue", which is not supported by many common load balancers, proxies and other things that might be between you and your server. No browsers use this header. I just tested this with and without a load balancer that does not support "expect 100" and confirmed that it breaks. I've filed a ticket with Wolfram Support. Yet another annoying part of the URLFetch/URLExecute/URLRead changes. $\endgroup$ Commented Oct 14, 2016 at 3:07