Authorization failure not properly detected #8
Labels
No labels
dependencies
javascript
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
quodatum/basex-node#8
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Hi,
I'm using basex-node with BaseX 7.6 and it appears that authorization rejections are not properly detected. As far as I have determined, the server replies with '\u0001' if the login was incorrect, but the state machine in the Session constructor does not properly interpret that response and carries on as if authorization was successful. I do not quite understand the popByte function as it is, maybe it is something that you can fix easily?
Thanks (and thanks for basex-node anyway!)!
Hans
Hi Hans,
Yes, it was a regression. Should be fixed in 0.61 now on github and npm.
Works perfectly, thanks for the quick turnaround!
-Hans
On Sun, Feb 17, 2013 at 6:05 PM, Andy Bunce notifications@github.comwrote: