We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Took me a while to figure this out (and still don't know why cht.sh is doing this) but for some queries the second snippet returns 404 (but the next ones work again) 🤔
But this issue is about handling it better, as this extension shows this:
Maybe a 404 could be shown as such?
The text was updated successfully, but these errors were encountered:
Oh damn I just saw it returns HTTP 200:
$ http https://cht.sh/rust/flush+stdout/1 HTTP/1.1 200 OK Connection: keep-alive Content-Length: 1611 Content-Type: text/plain; charset=utf-8 Date: Fri, 03 Mar 2023 15:57:31 GMT Server: nginx/1.13.12 Strict-Transport-Security: max-age=63072000; includeSubdomains X-Content-Type-Options: nosniff X-Frame-Options: DENY /* * 404 NOT FOUND * * Unknown cheat sheet. Please try to reformulate your query. * Query format: */ /LANG/QUESTION // Examples:
Sorry, something went wrong.
I opened a bug report on cheat.sh as that's kinda weird anyways:
chubin/cheat.sh#377
Yeah, I think that this response from cht.sh looks fine:
/* * 404 NOT FOUND * * Unknown cheat sheet. Please try to reformulate your query. * Query format: */ /LANG/QUESTION // Examples: /python/read+json
But if the configuration option "verbose" is false, then the response looks weird. I think we can fix that
VladBrok
Successfully merging a pull request may close this issue.
Took me a while to figure this out (and still don't know why cht.sh is doing this) but for some queries the second snippet returns 404 (but the next ones work again) 🤔
But this issue is about handling it better, as this extension shows this:
Maybe a 404 could be shown as such?
The text was updated successfully, but these errors were encountered: