invalid protocols #5

Open
opened 2015-01-06 14:14:52 -08:00 by jcblw · 1 comment
jcblw commented 2015-01-06 14:14:52 -08:00 (Migrated from github.com)

I got this error, I think we can avoid this by handing the 'error' event. I don't know how I got it, but it had something to do with an invalid url.

screenshot from 2015-01-06 14 09 51

I got this error, I think we can avoid this by handing the 'error' event. I don't know how I got it, but it had something to do with an invalid url. ![screenshot from 2015-01-06 14 09 51](https://cloud.githubusercontent.com/assets/578259/5637237/46f21fd2-95ae-11e4-87ce-fb52f25224e4.png)
jcblw commented 2015-01-06 17:53:14 -08:00 (Migrated from github.com)

I know what it is now, so when a protocol relative url is used. eg //google.com this is what happen. I think just catching and logging the error should suffice.

I know what it is now, so when a protocol relative url is used. eg `//google.com` this is what happen. I think just catching and logging the error should suffice.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
andyburke/node-storehouse#5
No description provided.