Re: 401 error

[Magdalen Berns <m berns thismagpie com>]

I am unfamiliar with this API so I can't say much about your problem, but I had a little look at the git log and I reckon following commit might include a change which is relevant to your problem with the update:

 

https://git.gnome.org/browse/libsoup/commit/?id=78e74de238479c2cc316cf6f888c53ddd087b51b

If things still don't make sense after that maybe try commenting on the bug or ccing  the committer (assuming I have identified the right commit above, that is!)

Maybe this document could also be useful:

https://developer.gnome.org/libsoup/stable/SoupCookie.html

Good luck!

Magdalen

On Thu, Jul 16, 2015 at 12:14 PM, Sam Bull <sam hacking sent com> wrote:

I've failed to get any response at all from the GNOME shell list, so I'm
posting this to a couple of other related lists, to see if I can get any
support. My extension has stopped working in GNOME 3.14+ due to a 401
error. Can anybody help with this? Details below.

On Sat, 2015-06-20 at 00:45 +0100, Sam Bull wrote:
> On Sat, 2015-06-13 at 10:54 +0100, Sam Bull wrote:
> > On Mon, 2015-06-01 at 09:53 +0100, Sam Bull wrote:
> > > In GNOME Shell 3.14, on Ubuntu 15.04, my extension is no longer able to
> > > sync to Owncloud due to a 401 error. Is there a change to
> > > Soup.message.new() that causes it to use cookies or something? I am
> > > trying to authenticate by passing the username/password in the URL. I'm
> > > not sure if there is an option to disable cookies or something else I
> > > need to do to get the authentication working.
> > >
> > > Details: https://github.com/owncloud/notes/issues/109
> > >
> >
> > Does anybody have any idea? I still haven't got this working.
> >         Soup.Message.new("GET",
> >         "http://user:pwd owncloud url/index.php/apps/notes/api/v0.2/")
> > just keeps giving a 401. I can test this in curl and it works fine. This
> > used to work before I upgraded to Ubuntu 15.04/GNOME 3.14. This is also
> > broken on my Gentoo box with GNOME 3.14, where it was working fine on
> > 3.12.
>
> So, further research has led me to try connecting to the 'authenticate'
> signal of the session, but this never gets triggered. So, I figured that
> maybe I need to explicitly enable authentication, but the functions to
> do this don't work. The error I get is:
>
>         (gnome-shell:1470): libsoup-WARNING **: soup-session.c:887:
>         invalid property id 18 for "add-feature-by-type" of type
>         'GParamGType' in 'SoupSession'
>         (gnome-shell:1470): Gjs-WARNING **: JS ERROR: TypeError:
>         httpSession.add_feature_by_type is not a function
>
> With the code:
>
>         const httpSession = new Soup.Session();
>         httpSession.add_feature_by_type(Soup.TYPE_AUTH_BASIC);

_______________________________________________
desktop-devel-list mailing list
desktop-devel-list gnome org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list