Thanks, I found the workaround about unchecking "use HTTP 1.1", and that seemed to fix the problem. Also it looks like MS is releasing and update today 8/22 to fix this.