Skip to content

How to handle unexpected responses #10

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

Closed
arielvalentin opened this issue Aug 30, 2019 · 0 comments · Fixed by #11
Closed

How to handle unexpected responses #10

arielvalentin opened this issue Aug 30, 2019 · 0 comments · Fixed by #11
Assignees

Comments

@arielvalentin
Copy link

I am new to using remote-input-element and am trying to figure out a way to properly handle unexpected HTTP responses.

It looks like this component will always replace the target container with the HTTP response body, however if the server responds with an unexpected response e.g. HTTP 500 or 502 with a Full HTML page instead of a fragment to display, then the output does not look very desirable.

https://user-images.githubusercontent.com/236297/61644279-6a3ad300-ac72-11e9-905c-0295859be893.png

What would be the best way to handle scenarios like this?

@muan muan self-assigned this Sep 10, 2019
@muan muan closed this as completed in #11 Sep 10, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants