Hi Bryan - Thanks for the info but no dice. app.config http_url_encoding
is "on" but the key shows as not found.
Anything else I can try?
Jim
On 10/25/11 8:26 AM, "Bryan Fink" wrote:
>On Tue, Oct 25, 2011 at 10:35 AM, Jim Adler wrote:
>> Hi Bryan - I'm now running 1.0.1 but the keys were inse
On Tue, Oct 25, 2011 at 10:35 AM, Jim Adler wrote:
> Hi Bryan - I'm now running 1.0.1 but the keys were inserted under 0.14. I
> tried your test and it worked fine. So, maybe I'm caught between
> inserting under an old version and now reading under another?
It's possible that your upgraded node
Hi Bryan - I'm now running 1.0.1 but the keys were inserted under 0.14. I
tried your test and it worked fine. So, maybe I'm caught between
inserting under an old version and now reading under another?
Thanks for your help.
Jim
On 10/25/11 7:02 AM, "Bryan Fink" wrote:
>On Tue, Oct 25, 2011 a
On Tue, Oct 25, 2011 at 12:54 AM, Jim Adler wrote:
> Ok, this is a little simpler but I'm not sure how to proceed. When I pull
> the keys via ?keys=stream API, I have a key "name-this\nBob". But
> fetching it gets me a 404 not found error. I've tried %0D%0A (and other
> variants) in the API call
Ok, this is a little simpler but I'm not sure how to proceed. When I pull
the keys via ?keys=stream API, I have a key "name-this\nBob". But
fetching it gets me a 404 not found error. I've tried %0D%0A (and other
variants) in the API call but no luck. Any way to delete this errant key?
Jim
From:
