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
having an api method to request a user version at a specifc timestamp /api/v1/users/:userId/version-at/:timestamp
/api/v1/users/:userId/version-at/:timestamp
this call fails, when a user types any value in the timestamp parameter field containing a space. the entire chrome tab crashes.
this is not related to timestamp itself, as any other field that is passed into the URL has the same behavior.
at least fields of the type: "path" should get a default urlEncode() over them. this will transform spaces in %20 among other characters ...
%20
you could argue that the user should know that, but it's kind of a shame that the entire tab just hangs or crashes.
server console window reports the following:
in processRequest json: { oid: '5441c14cf1a0caa315a0ca2d', timestamp: '2014-11-14 00:00' } locations: { oid: 'path', timestamp: 'path' } Unsecured Call Protocol: HTTP error: socket hang up
The text was updated successfully, but these errors were encountered:
No branches or pull requests
having an api method to request a user version at a specifc timestamp
/api/v1/users/:userId/version-at/:timestamp
this call fails, when a user types any value in the timestamp parameter field containing a space. the entire chrome tab crashes.
this is not related to timestamp itself, as any other field that is passed into the URL has the same behavior.
at least fields of the type: "path" should get a default urlEncode() over them.
this will transform spaces in
%20
among other characters ...you could argue that the user should know that, but it's kind of a shame that the entire tab just hangs or crashes.
server console window reports the following:
The text was updated successfully, but these errors were encountered: