GNOME Bugzilla – Bug 574773
Add API to disable SoupSessionFeatures from SoupMessages
Last modified: 2009-08-09 15:03:18 UTC
Hi, I have the use case of not wanting to use the proxy settings for certain messages. Right now I'm using another session that doesn't have a proxy to do it, but I think it makes sense to have a SOUP_MESSAGE_NO_PROXY flag for that purpose.
As discussed on IRC, I'm not totally sure this is the right solution. Then again, it's VERY similar to the existing NO_REDIRECT flag, so... Maybe what we really need is a per-message way to disable particular session features, so you can queue a message without proxy resolution, or without cookies, or without authentication, or (eventually) without Content-Encoding support, etc.
Retitling, as discussed on IRC. The API to disable some SoupSessionFeatures from SoupMessages sounds good and would solve my use cases (not only this one but another with SoupCookieJar). As talked on IRC, a possibility of the public API would be something like soup_message_disable_feature (msg, SOUP_TYPE_PROXY_RESOLVER) danw> SoupMessagePrivate would have a GSList or something of disabled features, and the session would call soup_message_get_disabled_features() or whatever
Created attachment 139740 [details] [review] Add soup_message_disable_feature() This allows you to disable specific SoupSessionFeatures for particular messages. Also update tests/sniffing-test to test it out.
*** Bug 590436 has been marked as a duplicate of this bug. ***
committed