abdera-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From herbert <i...@gmx.de>
Subject Re: HTTP-GET-Problem with Abdera-Client 0.3.0.
Date Wed, 12 Dec 2007 10:47:45 GMT

Hi James!

Though the "revertRedirectSetting"-option looks a bit obscure, it has the
that it preserves the value of followRedirects defined by the
if revertRedirectSetting is not set to true and overrides the default-value,
if set to true
 (...and thus by just using one additional parameter).

The current solution has the caveat, that the DeleteMethod, the
OptionsMethod and
the TraceMethod will by default have followRedirects set to true. 
Prior to this change, they had followRedirects set to false.

But I don't know, if there are reasons for this default-settings in

For my purposes the current solution is totally fine!



James M Snell wrote:
> I'm not sure about the isRevertRedirectSetting, but a getter and setter
> on the RequestOptions is good.  I've just checked in that change to trunk
> - James
> herbert wrote:
>> Hi Chris!
>> My solution would be adding a property followRedirects to the class 
>> RequestOptions.
>> Next change would be in the method createMethod() of the class
>> MethodHelper.
>> After creation of the concrete HTTP-Method I would insert the following
>> line:
>> httpMethod.setFollowRedirects(options.isFollowRedirect());
>> (Or another version, introducing a property revertRedirectSetting to the
>> class 
>> RequestOptions. And then in createMethod():
>> if (options.isRevertRedirectSetting()) {
>>   httpMethod.setFollowRedirects(!httpMethod.getFollowRedirects());
>> })
>> Dunno, if these are generic approaches, that are interesting for others?
>> Regards, Herbert

View this message in context: http://www.nabble.com/HTTP-GET-Problem-with-Abdera-Client-0.3.0.-tp14212795p14292635.html
Sent from the abdera-user mailing list archive at Nabble.com.

View raw message