Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Validate responses client side #242

Open
GentlemanHal opened this issue Aug 21, 2018 · 1 comment
Open

Validate responses client side #242

GentlemanHal opened this issue Aug 21, 2018 · 1 comment
Labels
low priority Changes the team are unlikely to work on any time soon, consider submitting a PR

Comments

@GentlemanHal
Copy link
Member

We had an issue at work which resulted in a e.filter is not a function error (the e is because we are using the minified production build).

After a little investigation it seems the issue was the web proxy. It decided to not allow the calls to the Nevergreen server and was returning a OK status but with a html webpage instead of json. So I suspect the code is just getting back a string instead of an array.

This is low priority as the only way something like this should ever happen is some kinda of proxy problem and if your proxy is broken then nothing is going to work anyways, but it would be nice to display a more informative and potentially helpful error message.

@GentlemanHal GentlemanHal added the low priority Changes the team are unlikely to work on any time soon, consider submitting a PR label Aug 21, 2018
@GentlemanHal GentlemanHal changed the title filter is not a function (web proxy issue) Validate responses client side Nov 14, 2022
@GentlemanHal

This comment was marked as resolved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
low priority Changes the team are unlikely to work on any time soon, consider submitting a PR
Projects
None yet
Development

No branches or pull requests

1 participant