- From: Carlos Tejo Alonso <carlos.tejo@fundacionctic.org>
- Date: Tue, 23 Dec 2008 19:23:53 +0100
- To: "Al Gilman" <Alfred.S.Gilman@IEEE.org>
- Cc: <www-talk@w3.org>
- Message-ID: <09700B613C4DD84FA9F2FEA52188281902BB143D@ayalga.fundacionctic.org>
>> Maybe I have express myself wrong. I will try again with an example: >> I am abroad, using a shared pc with arabic language as default. I >> send a >> request to the URL http://www.example.org/doc. By content >> negociation, a >> server will response with a page written in arabic. In that moment, I >> want to change the language of the content, and the return page >> should >> be again http://www.example.org/doc. >> What would be the correct approach ? >> - a link that invokes a HTTP GET method >> - a button that invokes a HTTP POST method > > It seems to be that you're changing the state of the server, thus > GET would be incorrect. I disagree. The Accept-Language: header is responded to in the reply to the GET request containing it and does not alter state on the server. The server is ready on the next hit from anyone to provide the same range of languages as on this hit. With the same server defaults, not defaulting to the last request satisfied. If you click on the flag of your national language on a site to get that language version, that is changing the state of your session, yes. --- That's the problem: the way to interprete it. I am looking for a normative answer from W3C, but I haven't found yet anything in the documentation about it. Carlos Tejo
Received on Tuesday, 23 December 2008 18:23:47 UTC