Re: client-side chunked-encoding and certificates

[Dirk-Jan C. Binnema <djcb bulk gmail com>]

Thanks Sergio and Dan!

On Mon, Sep 30 2013, svillar igalia com wrote:

> On 28/09/13 16:51, Dirk-Jan C. Binnema wrote:

> Hi djcb!
>
> happy to hear from you :)

Yeah, same here. Time flies, doesn't it? :-)

> > I'm a happy libsoup-user, so thanks for all the hard work / thought that
> > went into it! I particularly like the API in comparision with
> > e.g. libcurl.
> >
> > However, libcurl has two features that libsoup doesn't seem to have:
> >
> > - client-side certificates, i.e. the ability to set a
> >   pkcs#12/pem/... certificate so the server can verify who I am.
>
> client side certificates work is tracked in
> https://bugzilla.gnome.org/show_bug.cgi?id=334021. Don't know if Dan has
> some extra details but seems like the work is blocked by some missing
> gio bits (perhaps a nice task for this year WebKitGtk hackfest Dan?)

Ah, that's good to know! I'll track that bug.

On Mon, Sep 30 2013, danw gnome org wrote:

> On 09/28/2013 10:51 AM, Dirk-Jan C. Binnema wrote:
> > - client-side certificates, i.e. the ability to set a
> >   pkcs#12/pem/... certificate so the server can verify who I am.
>
> As Sergio pointed out, this is something that's been on the to-do list
> forever. However, there is a good chance it will finally happen this
> release cycle.

That's nice to hear.

> (FWIW, I think it might actually be possible to do this with just the
> current APIs, with a little bit of work. Using the
> SoupMessage:network-event signal, you can get access to the
> GTlsConnection, and then you can fiddle with it before or during the
> handshake.)

Okay, I'll play a bit with that...

> > - client-side chunked encoding, i.e., the ability to send data to a
> >   server in chunks.
>
> This is possible, though not especially clean API-wise. It works the
> same way as server-side chunked encoding
> (https://developer.gnome.org/libsoup/stable/libsoup-server-howto.html#id-1.2.4.5.8);
> you set the encoding with soup_message_headers_set_encoding() before
> sending the message, and then add chunks with soup_message_append() /
> soup_message_append_buffer(), possibly listening to the wrote-chunk
> signal to know when another chunk is needed, and use
> soup_message_body_complete() when you're done.
>
> Eventually there will be a GOutputStream-based API for writing the
> request body, like the existing GInputStream-based ones for reading the
> response. But I'm not sure exactly when that will be.

Okay, I'll try if I can get that to work, too.

Again, thanks a lot for your work libsoup, it's a nice piece of work.

Cheers,
Dirk.

-- 
Dirk-Jan C. Binnema                  Helsinki, Finland
e:djcb djcbsoftware nl           w:www.djcbsoftware.nl
pgp: D09C E664 897D 7D39 5047 A178 E96A C7A1 017D DA3C