[
https://issues.apache.org/jira/browse/WINK-104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Rheinheimer updated WINK-104:
----------------------------------
Description:
HTTP Accept header can have q=0 quality factor. This indicates that the server
should NOT send out that encoding.
Please see patch for tests and possible solution. I will say, however, that I
don't particularly like the solution. It's readable, and it works, but it's
part of some filtering code that I think could be and should be optimized.
To whomever commits this, please open a followup Jira to optimize that
filtering code patch in ResourceRegistry.
If you change the solution significantly, please email me or I'll check the
Jira periodically to see if any updated patches were posted. I'm curious to
see the solution(s) and learn how I can make your job easier. :)
was:
HTTP Accept-Encoding header can have q=0 quality factor. This indicates that
the server should NOT send out that encoding.
Please see patch for tests and possible solution. I will say, however, that I
don't particularly like the solution. It's readable, and it works, but it's
part of some filtering code that I think could be and should be optimized.
To whomever commits this, please open a followup Jira to optimize that
filtering code patch in ResourceRegistry.
If you change the solution significantly, please email me or I'll check the
Jira periodically to see if any updated patches were posted. I'm curious to
see the solution(s) and learn how I can make your job easier. :)
Summary: handle q=0 on Accept http header (was: handle q=0 on
Accept-Encoding http header)
> handle q=0 on Accept http header
> --------------------------------
>
> Key: WINK-104
> URL: https://issues.apache.org/jira/browse/WINK-104
> Project: Wink
> Issue Type: Bug
> Components: Server
> Affects Versions: 0.1
> Reporter: Mike Rheinheimer
> Fix For: 0.1
>
> Attachments: WINK-104.patch
>
>
> HTTP Accept header can have q=0 quality factor. This indicates that the
> server should NOT send out that encoding.
> Please see patch for tests and possible solution. I will say, however, that
> I don't particularly like the solution. It's readable, and it works, but
> it's part of some filtering code that I think could be and should be
> optimized.
> To whomever commits this, please open a followup Jira to optimize that
> filtering code patch in ResourceRegistry.
> If you change the solution significantly, please email me or I'll check the
> Jira periodically to see if any updated patches were posted. I'm curious to
> see the solution(s) and learn how I can make your job easier. :)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
