| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Currently it has not practical use. I will rethink how to implement
this in nicer way in order to make one-request basic auths possible.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
It has been deprecated for a long while, and we were only using it for
proxy support. However, now that we switched to using SoupSession rather
than SoupSession{Sync,Async}, a default proxy resolver will be used, so
we don't need to set it explicitly.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
priv->session was a SoupSession since the last commit, which also
removed every practical usage or priv->session_sync.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This function can be helpful if one wants more control over libsoup
features than what librest simple API provide. For example, to get full
access to libsoup cookie API (say to be able to add arbitrary cookies to
the soup session), one can do:
RestProxy *proxy = g_object_new(REST_TYPE_PROXY,
"url-format", url,
"disable-cookies", TRUE,
NULL);
SoupSessionFeature *cookie_jar = SOUP_SESSION_FEATURE(soup_cookie_jar_new ());
rest_proxy_add_soup_feature(proxy, cookie_jar);
It's then possible to use all the soup_cookie_* methods to deal with
cookies.
https://bugzilla.gnome.org/show_bug.cgi?id=728340
|
|
|
|
|
|
| |
Syntax matters.
https://bugzilla.gnome.org/show_bug.cgi?id=712747
|
|
|
|
|
|
|
|
| |
The SoupLogger instance needs to be attached last (at least after the
SoupCookieJar librest uses), otherwise REST_DEBUG=proxy will not dump the
cookie headers added by the SoupCookieJar instance.
https://bugzilla.gnome.org/show_bug.cgi?id=712231
|
|
|
|
|
|
| |
This property maps to the SoupSession::ssl-ca-file property, and
allows to specify a file that contains the CAs to use to verify
the certificates we'll get during a TLS session.
|
|
|
|
|
|
|
|
| |
g_cclosure_marshal_generic() was only introduced in glib 2.30, for
older glib we need to specify the marshaller to use. If only NULL is
passed, we get a segfault when trying to invoke the signal.
https://bugzilla.gnome.org/show_bug.cgi?id=703642
|
|
|
|
| |
Need to use #ifdef here, not #if.
|
|
|
|
| |
--without-ca-certificates
|
|
|
|
|
|
|
|
| |
This will make it possible to pause/resume the current call
during authentication callbacks to be able to get back to
the mainloop to get authentication credentials.
https://bugzilla.gnome.org/show_bug.cgi?id=658937
|
|
|
|
|
|
|
|
|
|
| |
If caught by application, this signal can be used to set the
credentials to use when authentication is needed. If not caught,
librest behaviour will be unchanged (try to use what the
username/password properties were set to first, and don't try to reuse
them if this fails).
https://bugzilla.gnome.org/show_bug.cgi?id=658937
|
|
|
|
|
|
|
| |
This is needed in order to access REST services over https using
self-signed certificates.
https://bugzilla.gnome.org/show_bug.cgi?id=663786
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When provided with wrong credentials, libsoup will try to connect
and emit its 'authenticate' signal as long as its callback calls
soup_auth_authenticate. It will fail the request and report to
the caller if this function is not called. Since the 'retrying'
parameter to the 'authenticate' callback lets us know when the
credentials we provided are the wrong ones, this commit makes sure
we stop calling soup_auth_authenticate after trying the credentials
once. Without this, libsoup will try the same request again and
again without ever returning when provided with wrong credentials.
https://bugzilla.gnome.org/show_bug.cgi?id=658937
|
|
|
|
| |
Fixes: https://bugzilla.gnome.org/show_bug.cgi?id=675213
|
| |
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=658937
|
|
|
|
|
|
|
| |
By setting the CA file we make it a certificate error if the certificate
is self-signed.
Fixes: https://bugzilla.gnome.org/show_bug.cgi?id=663783
|
|
|
|
|
|
|
| |
This is neccessary for Vimeo because of a bug where we get a 500 error if we
pass along the cookie it provides.
Fixes: https://bugs.meego.com/show_bug.cgi?id=15015
|
| |
|
| |
|
|
|
|
| |
Signed-off-by: Gary Ching-Pang Lin <chingpang@gmail.com>
|
| |
|
|
|
|
|
|
|
| |
When adding a feature, the soup session takes a reference on the feature, so we
need to unref it after adding in order for it not to leak.
http://bugs.meego.com/show_bug.cgi?id=2500
|
|
|
|
|
|
|
|
| |
Use the completed callback in soup_session_queue_message instead of connecting
to finished on the message itself. I'm not entirely why the behaviour is
different but this fixes #842 where an async call make inside another async call
would end up with the original message "finishing" again, causing infinite
loops.
|
| |
|
|
|
|
| |
Fixes: http://bugzilla.meego.com/show_bug.cgi?id=273
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
This function is now used by the weak notify handler to cancel the call when
the weakly referenced object goes away.
|
|
|
|
|
| |
The functionality that these functions provided can be achieved using
RestProxyCall and rest_proxy_simple_run.
|
| |
|
| |
|
|\ |
|
| | |
|