#evehq

thats why i'm kind of at a loss

i think its got to do with my client. Does eve prefer any additonal headers be sent for a basic GET

hmm nope.. did you try with curl?

works with curl

lol

hmm

and i use livecode for tons of different web services and rest interfaces

don't know livecode

I currently use it most with MongoLab's REST interface, and am looking for a better MongoDB rest

never encountered problems like this before.

right, it was a commercial toolkit that is going open source this month

we use it for lots of internal apps

its not very popular, but pretty powerful if you gotta get dirty things done fast

well when it comes to processing requests, eve is just Flask really

I have a custom node rest api that I have been working on, but the features already availiable in Eve made my mouth water.

right, and I tested it against a more standard flask demo and it works well there too

unfortunately, my python skills are sub-par

can you compare livecode request w/ eve-demo-client's or curls?

to see what's different

there must be something different in that request

right

lemme fire up wireshark and get a more complete look

brb

also are you running curl against the very same API instance?

maybe there's something different between the two attempts *shrugs* like a different settings.py

nicola: any idea why werkzeug is spitting back 405 on PATCH even though I have ALL methoded enabled?

nope

i assume you're on the latest version?

of werkzeug?

yup

lemme double check

I remember issues with (very) old releases, I don't think yours is

interesting, it was updated a month ago to 0.9

i'm on 0.8.3

don't think that's the problem but you never know (I was developing Eve with older versions)

gonna go ahead and update

nicola: btw i see @cerberos on #pocoo, is that you?

no