Peter Kipping

I also have this problem using the RESTer client on firefox and macOS. Interestingly I was able to get a GET request to work: http://localhost:11434/api/tags. But with POST I get...

Here is the issue curl http://localhost:11434/api/generate \ -H "Origin: chrome-extension://bpoadfkcbjbfhfodiogcnhade..f" \ -d '{ "model": "llama3", "prompt": "Why is the sky blue?", "stream": false }' If you add a Origin header...

These REST clients seem to set a lot of headers by default. For me the problem one was origin Origin: moz-extension://e9e1ba1b-37f9-4d80-b97e-c3e2d9738009 The simplest fix is to change it to Origin:...

Hi, I have submitted pr #216 for this issue. Let me know if it needs any changes, thx

I then changed the put op because petId as a required field would have showed up in that one too but we don't want it there since petId is not...

Interestingly this whole thing is really a documentation error. Even without these changes you can manually add petId to the post and it will work but no one will know...

I should clarify that I'm talking about the swagger documentation Swagger UI is available at: http://localhost:9966/petclinic/swagger-ui.html. just in case that wasn't clear