incubator-clerezza-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Reto Bachmann-Gmuer <>
Subject Re: Reverting platform defaultacceptheader
Date Wed, 09 Mar 2011 22:32:46 GMT
As I mentioned in my comment

The effect of the 202 lines of the platform.defaultacceptheader bundle can
be achived by changing a single line of code (in a more perfoamnt fashion,
btw.). I did now this change of code and resolved the issue.

However this has serious downsides, which were probably the reasons
platform.defaultacceptheader was never added to the clerezza launchers.

I really don't the reason for all this fuss, if independent projects were
relying on this bundle nothing should have changed for them (as the bundle
is still in the repository) except maybe that the now would have to specify
the version number previously inherited from the clerezza parent.


On Wed, Mar 9, 2011 at 8:33 PM, Marco Zaugg <> wrote:

> I totally agree with Tsuy. We had big issues with Google, Bing and co.
> indexing Clerezza-based content.
> -1
> -----Original Message-----
> From: Tsuyoshi Ito []
> Sent: Mittwoch, 9. März 2011 15:44
> To:
> Subject: Reverting platform defaultacceptheader
> Hi all
> In issue CLEREZZA-325 the project paltform.defaultacceptheader has
> been deleted. Because search engines like google and bing are not
> indexing html pages correctly (bing is indexing rdf+json) we have to
> use the defaultacceptheader to set accept-header when no accept-header
> is set. This project is not included by default in the apache clerezza
> launcher so there are no side effects for other users.
> So, I vote -1 for the changes in CLEREZZA-325 until a solution to the
> problem described above is implemented
> Cheers
> Tsuy

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message