even "hello world" is broken

[billwoo]

Describe the bug

Unexpected end of JSON input

Did this error occur online or while using the dotnet try tool?

on-line

If it occurred using dotnet try, which version are you using?
(You can find the version by running dotnet try --version).

If it occurred online, please provide the URL where it happened

What kind of error was it?

• User Interface (UI): For example the output never displayed
• Service Error: For example "The service is temporarily unavailable. We are working on it"
• Other :

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [e.g. Windows 10, macOS]
• Browser [e.g. Chrome, Edge, Safari]

Smartphone (please complete the following information):

• Device: [e.g. iPhone6]
• OS: [e.g. iOS8.1]
• Browser [e.g. stock browser, Safari]
• Version [e.g. 22]

[jonsequitur]

Thanks, @billwoo. What is the URL where you saw the issue?

[billwoo]

https://interactivedotnet.azurewebsites.net/HelloWorld.md

Chrome/64 74.0.3729.157

[jonsequitur]

This looks like a duplicate of #198.

[akshita31]

@billwoo I had a similar issue and the problem was that my chrome browser was not setting the xsrf-token

It seems that I had the setting "Block Third Party cookies" on in chrome and due to that try.dot.net iframe was not able to set the required cookie.
So could you try disabling ad block and turn off that cookie setting and hard refresh the browser(Ctrl+F5) and checking if the issue still persists ?

[billwoo]

@akshita31 Thanks, seems to be working now in Win 10/Chrome. However, the web-page view is screwed up (on a 4k 15.6" screen) and requires manually adjusting screen magnification.

Use of 'IFrame ("obsolete") is a red-flag.

I still see no reason to use this when .NET Fiddle is available, and ... reliable.

[akshita31]

As discussed offline, we should handle this gracefully on the client side. So whenever we see a response other than 200, we should display an informative message to the user pointing to the github and possibly some article stating that they need to add trydotnet.microsoft.com to list of allowed cookies

[billwoo]

The contrary question: why should the site need to set cookies ?

[jonsequitur]

It's an absolutely fair question. This cookie is used to implement a common CSRF prevention technique. But we're planning to investigate other approaches.

As for other cookies we set, our cookie policy is detailed here: https://privacy.microsoft.com/en-us/privacystatement.