| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
The dav and http backends of the daemon now use libsoup3. Things
should work more or less the same as before.
One caveat is that the soup session no longer defaults to
ssl-strict, so it will no longer silently accept certificates.
This does not affect the DAV backend (it has its own handling
which is replicated in the soup3 port) but it does affect the
http backend.
Fixes: https://gitlab.gnome.org/GNOME/gvfs/-/issues/208
|
| |
|
|
|
|
|
| |
g_type_class_add_private and G_TYPE_INSTANCE_GET_PRIVATE have been
recently deprecated. Let's use rather G_DEFINE_TYPE_WITH_PRIVATE
and _get_instance_private() instead in order to prevent deprecation
warnings.
|
| |
|
|
|
|
|
|
| |
Async and sync methods differ one from other. Async methods have more
error checking. We don't need the sync methods, because http and dav
backends don't use them. Therefor remove the sync methods.
https://bugzilla.gnome.org/show_bug.cgi?id=754824
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Some webdav servers doesn't implement range requests, which are
necessary for a seek support. GVfsHttpInputStream doesn't handle this
case. Consequently g_seekable_tell returns a requested offset, however
g_input_stream_read returns bytes from a beginning of a file.
Return error if Content-Range header field is missing, or the range is
not valid. This change is needed to avoid data corruption when reading.
https://bugzilla.gnome.org/show_bug.cgi?id=754824
|
| |
|
|
|
|
|
| |
Handle a read after a seek past the end of the file by ignoring the
requested range not satisfiable http error (416) and simply returning 0.
https://bugzilla.gnome.org/show_bug.cgi?id=710534
|
| |
|
|
|
|
|
| |
Fix the SEEK_END offset calculation by reversing the sign of offset and
taking into account the offset of the previous seek.
https://bugzilla.gnome.org/show_bug.cgi?id=710534
|
| |
|
|
|
|
|
| |
Ensure that the range header is updated every time ensure_request() is
called in case it has been updated.
https://bugzilla.gnome.org/show_bug.cgi?id=710534
|
| |
|
|
|
|
|
|
|
| |
Previously, the dav backend would segfault when reading after a seek (or
also if you did a read_async() without an explicit send()/send_async()
first) because the stream from soup_request_send_finish() was not being
stored, so store it.
https://bugzilla.gnome.org/show_bug.cgi?id=710534
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Use libsoup rather than libsoup-gnome since libsoup-gnome is not
required anymore.
Bump the libsoup requirement to 2.42 to prevent a build failure with old
libsoups (undefined references to soup_session_request_uri).
Don't include individual libsoup headers as recommended by the libsoup
documentation.
https://bugzilla.gnome.org/show_bug.cgi?id=587890
|
| |
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=702624
|
| |
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=695834
|
|
|
Replace the hacky SoupInputStream with a new GVfsHttpInputStream that
is a wrapper around SoupRequest. (We need a wrapper stream rather than
just using SoupRequest directly because we want the stream here to be
seekable, which requires cancelling and re-sending the HTTP request
and getting a new underlying stream.)
The http and dav backends still use both a sync and an async
SoupSession, even though this is no longer necessary, since changing
this would require a lot of rewriting of code that currently works.
https://bugzilla.gnome.org/show_bug.cgi?id=687757
Signed-off-by: Tomas Bzatek <tbzatek@redhat.com>
|
