But nowhere is it set to UTF-8.


On 19 September 2013 14:00, jvelilla <notifications@github.com> wrote:

> In library/network/protocol/content_negotation/src/conneg_server_side.e:
>
> > +feature -- Encoding Negotiation
> > +
> > +	charset_preference (a_server_charset_supported: LIST [READABLE_STRING_8]; a_header: detachable READABLE_STRING_8): CHARACTER_ENCODING_VARIANT_RESULTS
> > +			-- `a_server_charset_supported' represent a list of charset supported by the server.
> > +			-- `a_header' represent the Accept-Charset header, ie, the client preferences.
> > +			-- Return which Charset to use in a response, if the server support
> > +			-- one Charset, or empty in other case.
> > +		note
> > +			EIS: "name=charset", "src=http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.2", "protocol=uri"
> > +		local
> > +			l_charset_match: READABLE_STRING_8
> > +		do
> > +			create Result
> > +			if a_header = Void or else a_header.is_empty then
> > +					-- the request has no Accept-Charset header, ie the header is empty, in this case use default charset encoding
> > +					-- (UTF-8)
>
> I don't see the contradiction, because we are using the default_charset if
> the client doesn't provide one to build the corresponding variant results.
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/EiffelWebFramework/EWF/pull/71/files#r6459681>
> .
>