[
https://issues.apache.org/jira/browse/CLEREZZA-325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13004551#comment-13004551
]
Reto Bachmann-Gmür commented on CLEREZZA-325:
---------------------------------------------
no the situation works independently if an accept-header is specified or not,
what changes is that if the server can produces two represenations with equal
quality, they one with higher server-side priority is produced rather than the
one with the media-type first in alphabetic sorting.
The artifact of ZZ-324 was not part of the launcher and no respective issue has
been raised, so it doesn't seem to have been much of an issue for clerezza
users.
Anyway, rather than discuss here we should write a generic template containing
the whole graphnode context in rdfa. Google does index RDF as well, and the
current default renderlet doesn't provided any of this content. In the example
above http://localhost:8080/test could have many (inverse) properties that are
completely hidden away.
> Have server side media-type priority list to use when the cleint accept
> header expresses equal preference for multiple available representations
> ------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CLEREZZA-325
> URL: https://issues.apache.org/jira/browse/CLEREZZA-325
> Project: Clerezza
> Issue Type: Improvement
> Reporter: Reto Bachmann-Gmür
> Assignee: Reto Bachmann-Gmür
>
> revert CLEREZZA-324 once this implemented
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
