Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Content Negotiation, new selector #109

Closed
harikt opened this Issue Feb 24, 2014 · 3 comments

Comments

Projects
None yet
2 participants

harikt commented Feb 24, 2014

When we create a new selector and later trying to removing doesn't work.

{"type":"http:\/\/www.w3.org\/Protocols\/rfc2616\/rfc2616-sec10.html","title":"Not Found","status":404,"detail":"Page not found."}

When looking into this what I can figure out was "NetworkError: 404 Not Found - http://api.localhost/apigility/api/content-negotiation/" the endpoint will be http://api.localhost/apigility/api/content-negotiation . See the one without / .

Did a grep -r content-negotiation vendor and lots of code. If I can figure out will look.

Thanks

Owner

weierophinney commented Feb 24, 2014

I think I know what's going on. I'll take a look shortly, after I work through a few other issues on my plate.

Owner

weierophinney commented Feb 25, 2014

I think this may be the same issue I fixed with e569116 (which was specific to the database adapter screens). I'll be addressing this particular screen, as well as the REST/RPC service screens, later today.

Owner

weierophinney commented Feb 27, 2014

@harikt This should be fixed as of 0d9c8fd

weierophinney added a commit to weierophinney/zf-apigility-admin that referenced this issue Aug 12, 2016

Merge pull request #109 from erwinkloosterboer/master
Added setenvif to apache vhost in order to pass authorization headers

weierophinney added a commit to weierophinney/zf-apigility-admin that referenced this issue Aug 12, 2016

weierophinney added a commit to weierophinney/zf-apigility-admin that referenced this issue Aug 12, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment