Eric Anderson eceb0ac2af fix(auth) blank password results in inability to authenticate ... Found myself in a vicious loop if I failed to type in a password when prompted in Chrome. Every refresh of the page would fall into the criton check with a blank password. Seems Chrome wouldn't clear the headers until I closed the browser and/or switched to a new incognito tab. Probably a user error, but still, this avoided the criton throw.		2016-09-06 09:48:10 +03:00
..
auth.js	fix(auth) blank password results in inability to authenticate	2016-09-06 09:48:10 +03:00
config.js	feature(password) password -> criton	2016-03-09 13:09:14 -05:00
exit.js	chore(exit) add ";"	2015-04-20 04:43:54 -04:00
markdown.js	feature(markdown) throw() -> throw	2016-03-28 16:15:04 -04:00
prefixer.js	chore(prefixer) add ";"	2016-02-04 14:59:39 -05:00
repl.js	chore(repl) rm ","	2015-02-18 04:43:30 -05:00
rest.js	feature(rest) rm auth	2016-05-24 22:35:24 +03:00
root.js	feature(root) rm path	2015-04-08 03:20:10 -04:00
route.js	feature(cloudcmd) add one-panel-mode	2016-06-15 22:57:39 +03:00
validate.js	feature(validate) add	2015-06-22 02:34:34 -04:00