On Tue, 2014-02-25 at 06:53 +0000, Michael Felsberg wrote:
> >>< HTTP/1.1 401 Unauthorized
> >>< Soup-Debug-Timestamp: 1392805687
> >>< Soup-Debug: ESoapMessage 1 (0x7fc097021dd0)
> >>< Set-Cookie: mail.liu.se=R408630383; path=/
> >>< Server: Microsoft-IIS/7.5
> >>< Set-Cookie: exchangecookie=...; expires=Thu, 19-Feb-2015 10:28:07
> GMT;
> >>path=/; HttpOnly
> >>< WWW-Authenticate: ...
> >>< WWW-Authenticate: Negotiate
> >>< X-Powered-By: ASP.NET
> >>< Date: Wed, 19 Feb 2014 10:28:06 GMT
> >>< Content-Length: 0
> >
> >I don't think the 401 is a good sign ...
>
> It is the only 401. But I have no idea what the problem is here.

        Hi,
just for your information, the 401 at the beginning is not a problem on
the evolution-ews side, it's the way it works (in libsoup, but most
likely in general as well):
a) evolution-ews asks libsoup to connect to an exchange server
b) server responses with 401
c) libsoup notices that the connection requires credentials and
   asks for them
d) evolution-ews provides credentials
e) libsoup tries again with provided credentials

and if it fails with the credentials, then something goes wrong and most
likely the process continues at c).
        Bye,
        Milan

_______________________________________________
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list

Reply via email to