[webkit-qt] Currently Missing Features with QtWebkit / QNetworkAccessManager
rich at kde.org
Wed Aug 11 05:40:07 PDT 2010
On Fri, Jul 9, 2010 at 8:38 AM, Dawit A <adawit at kde.org> wrote:
> 1.) Add a new class for filtering requests without having to inherit from
> QNetworkAccessManager, something like a QNetworkRequestFilter class, which can
> be added and removed from QNAM to be used as a request filter.
I've started working on a QNetworkCustomReply class which I'll blog
about once I've finished (and then see if it can be worked up as a
MR). I'm still thinking about how a QNetworkRequestFilter would look.
> Dawit A.
> On Thursday, July 08, 2010 16:20:17 Richard Moore wrote:
>> These are the issues I'm aware of with the QtWebkit/QNAM combination
>> as a platform for browsers. It's possible that some of these issues
>> are incorrect and are supported somehow I'm not aware of, if so please
>> say so as that would be great! Note, don't take this as a criticism,
>> it's intended more as a way of organising what remains to be done.
>> * No support for OCSP (online certificate status protocol)
>> * No support for SNI (server name indication) see QTBUG-1352
>> * No support for EV certificates
>> * No support for DNS pinning (a way of avoiding DNS rebinding attacks)
>> * Incorrect case-sensitivity in MIME type handling (webkit bug #28654).
>> This one is waiting on me (or someone else) finding time to write
>> the test cases.
>> Anyone got anything to add to this todo list?
>> webkit-qt mailing list
>> webkit-qt at lists.webkit.org
> webkit-qt mailing list
> webkit-qt at lists.webkit.org
More information about the webkit-qt