Thanks Matt, André. I totally forgot the fact that QNetworkRequest has
attributes for controlling request behavior. It looks like a suitable place
for adding redirection control.
Peter,
I'm also looking at first enabling this on a per-request basis and then
extend it to QNAM. By 2 commits, do you
Mandeep Sandhu schreef op 31-1-2014 13:47:
> Hi All,
>
> I needed a suggestion on an API I'm adding to QNetworkAccessManager
> and co.
>
> I'm adding a HTTP redirect feature to QNAM. It can be enabled at a
> global (QNAM) level, or can be enabled/disabled on a per request
> (QNetworkRequest) bas
On 01/31/2014 01:47 PM, Mandeep Sandhu wrote:
> (...)
> The QNAM setting can be a simple bool which defaults to 'false' if not
> explicitly set by the user. However, the request level setting needs 3
> states - true (follow redirects), false (don't follow) and unset (use
> global setting).
How abo
On Friday, January 31, 2014, Mandeep Sandhu
wrote:
> Hi All,
>
> I needed a suggestion on an API I'm adding to QNetworkAccessManager and co.
>
> I'm adding a HTTP redirect feature to QNAM. It can be enabled at a global
> (QNAM) level, or can be enabled/disabled on a per request (QNetworkRequest)
Hi All,
I needed a suggestion on an API I'm adding to QNetworkAccessManager and co.
I'm adding a HTTP redirect feature to QNAM. It can be enabled at a global
(QNAM) level, or can be enabled/disabled on a per request (QNetworkRequest)
basis. The per-request setting, if set, overrides the global on
