Hi Mike,
Thanks for your reply. I had suspected that they were not implemented.
Note that I received a "403 Forbidden" rather than a "405 Method Not
Allowed" when doing the DELETE. I've now also tested PUT and found that
it has the same issue.
Given this restriction, I will probably end up using Apache Tomcat or
Jetty to intercept the requests, and make XDBC requests to Mark Logic
from there. This will give me full URL mapping ability too.
-- Steve
Michael Blakeley wrote:
Steve,
The misleading error message for DELETE with application-level
authentication is a bug, and I understand that a fix is in the works
for a future release. As you found, switching to HTTP authentication
results in the correct error message (405).
There is an open RFE for HTTPServer support for the DELETE method, but
I can't speak to its implementation status. Meanwhile, support for
DELETE, PUT, and OPTIONS can be implemented via request-rewriting. One
approach is to create a simple Apache module, which rewrites each
method to a POST with a method={$VERB} request-field.
-- Mike
Steve Mallen wrote:
Hi folks,
I've been trying to implement a simple REST-style API using the Mark
Logic HTTP server and an XQuery controller. This has been going
fairly well; but I've hit a bit of a brick wall with the DELETE method:
I have my HTTP server set up with authentication: "application-level"
and default user: "admin", in order to effectively turn off security
(I'm just doing some prototypying here).
When I submit a DELETE request to the server I get a "500 Internal
Server Error" response code, with this message:
SEC-DEFAULTUSERDNE: Default user does not exist: sec:user-id =
7561169777825101503
GET and POST requests are working fine, by the way. I haven't tried
the PUT method yet.
To try and get around this, I turned security on by setting
authentication to "basic", and sending the username and password
credentials to the server. I then get:
403 Forbidden
There is no clue as to why the request has been denied. Does this
basically mean that the "DELETE" method isn't supported? I tried to
test this assumption by doing an "OPTIONS" request, which predictably
gave me:
405 Method Not Allowed
Any help or clues on this would be much appreciated.
Many thanks,
-Steve
_______________________________________________
General mailing list
[email protected]
http://xqzone.com/mailman/listinfo/general
_______________________________________________
General mailing list
[email protected]
http://xqzone.com/mailman/listinfo/general
_______________________________________________
General mailing list
[email protected]
http://xqzone.com/mailman/listinfo/general
