Closed mirzov closed 8 years ago
Hello @mirzov It seems to me you are right. Accordingly to RFC 7232 (which supersedes RFC 2621) the ETag must be in quoted strings.
I created a JIRA issue to track progress on this: https://softinstigate.atlassian.net/browse/RH-207
However, I can't give you the ETA right now, we need to prioritize work internally.
Hello @mkjsix, Thank you for the prompt reaction! The issue is not critical as far as I am concerned (results in warnings by an HTTP-level library). Hope the change will not create problems for your existing user base.
Not sure about the impact, but we'd like to stay HTTP compliant as much as possibile. We'll publish the changes on master and then decide when to move to a stable release.
Hi @mirzov Unfortunately we have an impact already with our default integration tests, so we do expect regressions. This means we need to schedule this modification for a major release (3.0) as it could probably break clients using 2.x.
Hi @mkjsix Thanks a lot for letting me know, appreciate your fast feedback!
After a deeper analysis this would really require a major refactoring, so we have decided to freeze this activity because we have higher priorities for the product. Technical details are in https://softinstigate.atlassian.net/browse/RH-207
Hi! According to RFC 2616, the values of the ETag headers are supposed to be quoted strings. Please see also this answer on StackOverflow. Do you think you could consider complying and changing the RESTHeart responses in future releases?