You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Writing graphite/shadow checks, I end up with a lot of characters (*, {, <, ...) that require url-encoding. Otherwise, you get an exception from the http request (which is masked and shown to the user as "Error connecting...").
Two options:
URL-encode the path that the user gives (either before storing it to the DB, or each time before running the check). This will allow the user to supply a more human-readable URL, but will confuse a user that supplies a URL that's already encoded.
Check the validity of a URL by parsing it using the same library that http/get uses. If this fails, alert the user instead of allowing him/her to set a bad check.
Thoughts?
The text was updated successfully, but these errors were encountered:
Writing graphite/shadow checks, I end up with a lot of characters (
*
,{
,<
, ...) that require url-encoding. Otherwise, you get an exception from the http request (which is masked and shown to the user as "Error connecting...").Two options:
http/get
uses. If this fails, alert the user instead of allowing him/her to set a bad check.Thoughts?
The text was updated successfully, but these errors were encountered: