Skip to content
This repository has been archived by the owner on Nov 10, 2017. It is now read-only.

VideoServiceClient BadRequest when creating operation #2

Open
margaretmz opened this issue Jul 7, 2016 · 2 comments
Open

VideoServiceClient BadRequest when creating operation #2

margaretmz opened this issue Jul 7, 2016 · 2 comments

Comments

@margaretmz
Copy link

From @theofanis on June 3, 2016 14:51

I'm using video api version 1.0.1 from nuget.

When calling CreateOperationAsync with a videoUrl parameter and MotionDetectionOperationSettings I always get a bad request.

Observing the request using Fiddler the request is as follows (key and url are fake for this sample):

POST https://api.projectoxford.ai/video/v1.0/detectmotion HTTP/1.1
ocp-apim-subscription-key: xxxxxxxxxxxxxx
Content-Type: application/json; charset=utf-8
Host: api.projectoxford.ai
Content-Length: 55
Expect: 100-continue
Connection: Keep-Alive

"https://localhost:8888/videos/test.mp4"

This isn't a json payload.

Copied from original issue: microsoft/ProjectOxford-ClientSDK#71

@margaretmz
Copy link
Author

From @cthrash on June 3, 2016 15:26

You are correct - that is a bug.
For now, instead of using MotionDetectionOperationSettings, call with OperationType.DetectMotion and it should work. Ignore the 'obsolete' warning.

@margaretmz
Copy link
Author

From @theofanis on June 7, 2016 10:36

I went with making the call using HttpClient, this was for a hackathon and needed a fast and dirty solution.

Thanks for your reply and excuse my late reply.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant