These are chat archives for deployd/deployd

Apr 2015
Benjamin Schuster-Boeckler
Apr 25 2015 12:56
there's something funny going on with query parsing
results in this: metadata:get { id: 94633006720 } +115ms
(I just did a console.log(query) in the first line of the resource script)
it seems that the query component gets interpreted as a number somewhere, and then looses the leading 0
it's definitely still ok at the routing stage. When I run the server with DEBUG="*", I get:
router routing /metadata?id=094633006720 to /metadata +7ms
any idea how to fix this?