chemistry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Florian Müller (JIRA) <>
Subject [jira] [Commented] (CMIS-811) Support HEAD and OPTIONS methods for Browser & AtomPub Bindings
Date Fri, 13 Jun 2014 08:36:02 GMT


Florian Müller commented on CMIS-811:

I have two questions regarding this patch.

* To implement HTTP OPTIONS correctly, the repository capabilities and the Allowable Action
have to be taken into account. If a repository doesn't support a certain feature (= returns
the HTTP status code 405), OPTIONS shouldn't indicate that the client could do that. Do you
have a use case that requires (generic) HTTP OPTIONS support?
* The patch determines the content length for HTTP HEAD requests and sets the Content-Length
header. But the Content-Length header is not set in HTTP GET responses. The content is sent
in chunks instead. That is, the headers of HEAD and GET would be different, which is not the
intention of HTTP HEAD. Is there a reason for that?

> Support HEAD and OPTIONS methods for Browser & AtomPub Bindings
> ---------------------------------------------------------------
>                 Key: CMIS-811
>                 URL:
>             Project: Chemistry
>          Issue Type: Improvement
>          Components: opencmis-client-bindings
>    Affects Versions: OpenCMIS 0.11.0
>            Reporter: Tom Weinschenk
>            Assignee: Florian Müller
>            Priority: Minor
>              Labels: patch
> Browser and AtomPub Bindings for Apache Chemistry OpenCMIS do not currently support HTTP
HEAD and OPTIONS methods. While not as common as the four primary HTTP REST methods, these
methods are worthy of support within Apache Chemistry OpenCMIS.
> Pull request at

This message was sent by Atlassian JIRA

View raw message