I don't recall why accept was dropped (probably overzealous filtering). It probably hasn't come up before because most people don't seem to actually use HTTP header semantics. You should file a bug for this.
On Thu, Sep 24, 2009 at 10:47 AM, David Boyer <[email protected]> wrote: > Make Request strips a number of headers including Accept from an > outgoing makeRequest on it's way to the target server. We have data > that can comeback as JSON or as XML, but the default (no Accept) > header is xml. What gives. We add ContentType.JSON to the > makeRequest, and add params[gadgets.io.RequestParameters.HEADERS] = { > "accept": "text/json" } to the request params, but of course the > buildHttpRequest in MakeRequestHandler prevents the Accept header from > going through. MakeRequestHandler.BAD_HEADERS... > > We need a solution that works, here. > > I've searched the mailing list, and I can't see any discussion of > Accept is being throttled. If you are going to strip the Accept > header, then I had expected that the ContentType.JSON setting in > makeRequest would somehow translate into an Accept header being added > by the MakeRequestHandler, but it's not. > > -- > David S Boyer > [email protected] > 703.499.8728(h) > 703.408.5395(m) >
