| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
| |
Actually, the RFC 2109 says cookies should not be stored if the path
attribute is not a prefix of the request URI the cookie comes from.
However, all browsers allow it anyway; with the demo browser e.g.
logging in to wordpress.com was not possible.
We still do path checking when sending cookies, i.e. in
QNetworkCookieJar::cookiesForUrl().
Reviewed-by: Markus Goetz
Task-number: QTBUG-5815
|
|
|
|
|
|
|
|
| |
Seems like WinHttpGetIEProxyConfigForCurrentUser can return more
than one proxy even if this is not documented.
Task-number: QTBUG-5981
Reviewed-by: Peter Hartmann
|
|
|
|
| |
Reviewed-by: Peter Hartmann
|
|
|
|
| |
Reviewed-by: TrustMe
|
|\ |
|
| |
| |
| |
| | |
Over src/ tools/ examples/ and demos/
|
|/
|
|
|
|
|
|
|
| |
The select() system call was used in the wrong way.
We need to select for exceptions too.
Task-number: QTBUG-5799
Reviewed-by: Aleksandar Sasha Babic <aleksandar.babic@nokia.com>
Reviewed-by: Peter Hartmann
|
|
|
|
|
|
| |
Don't use QFile's Qt3support member, use fileName() instead.
Reviewed-by: Trust me
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The QFileNetworkReply is a wrapper around QFile that
has therefore similar performance. This avoids
the usage of the unperformant QNetworkAccessFileBackend.
The benchmark qfile_vs_qnetworkaccessmanager shows
that the QFileNetworkReply's performance is better
than 0.9x of QFile compared to QNetworkAccessFileBackend
which had about 0.5x of QFile.
Reviewed-by: Peter Hartmann
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The QDateTimeParser forces at least two QString allocations
to convert the Month string into a integer. This makes parsing
the date string the most expesnsive operation from within
replyHeaderChanged.
Use sscanf to parse the RFC1123 header to get a significant
speedup. Use a switch case statement to convert the month
name to a integer.
Reviewed-By: Markus Goetz
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
toLower will force a memory allocation, and memory allocations
are certainly adding a delay. Use qstricmp were this is easily
possible. This change makes headerValues et all drop out of
the profile.
QChar::toLower will now be called more often, specially for
loops that do linear searching. In the profile with real web
content this is faster than using QByteArry::toLower in the
inner loop and the forced memory allocations.
Reviewed-By: Markus Goetz
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Using qstricmp is faster on the desktop than the alloc of
QByteArray::toLower and the QByteArray::operator==.
QChar::toLower will now be called for the input key from
within the loop. In the measurements done this is still
a performance improvement over the allocation done by
QByteArray::toLower. For more header values this might
not be the case anymore.
RESULT : tst_Loading::byteArrayTestLower():
0.00076 msec per iteration (total: 25, iterations: 32768)
RESULT : tst_Loading::byteArrayTestCompare():
0.00028 msec per iteration (total: 37, iterations: 131072)
Reviewed-By: Markus Goetz
|
| |
| |
| |
| |
| |
| |
| | |
HTTP header names are case insensitive, but stick to what all browsers
etc. use to work around buggy servers.
Reviewed-by: TrustMe
|
| |\ |
|
| | |
| | |
| | |
| | |
| | |
| | | |
Inspired by merge request 2012 by Joel Nordell
Reviewed-by: Peter Hartmann
|
| | |
| | |
| | |
| | | |
Reviewed-by: Peter Hartmann
|
| |/
|/|
| |
| |
| |
| |
| |
| | |
HTTP header names are case insensitive, but stick to what all browsers
etc. use to work around buggy servers.
Task-number: QTBUG-5618
Reviewed-by: Peter Hartmann
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
instead than when parsing the cookie header.
This corrects the bug QT-2379, happening in the following sequence:
parseCookie -> setCookieUrl -> toRawForm -> parseCookie
where a default domain would now also have a dot prefix, and shouldn't.
QT-2379
Reviewed-by: Peter Hartmann
|
|\ \ \
| | |/
| |/|
| | |
| | |
| | |
| | | |
Conflicts:
configure.exe
src/corelib/io/qfsfileengine.cpp
tests/auto/qfile/tst_qfile.cpp
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
patch by Warwick Allison. On cleanup in QHostInfoAgent, we were waiting
forever for the thread to terminate, which did not always succeed due to
a Linux kernel bug. Now, we just wait for some time and then return
anyway.
Reviewed-by: Marius Storm-Olsen
Task-number: QTBUG-5296
|
|\ \ \
| | |/
| |/| |
|
| |\ \ |
|
| | | |
| | | |
| | | |
| | | | |
Reviewed-by: Trust Me
|
| |/ /
| | |
| | |
| | | |
Reviewed-by: Friedemann Kleint <friedemann.kleint@nokia.com>
|
|\ \ \
| |/ / |
|
| |\ \
| | | |
| | | |
| | | |
| | | |
| | | | |
Conflicts:
src/gui/kernel/qevent.cpp
src/network/ssl/qsslerror.cpp
|
| | | |
| | | |
| | | |
| | | | |
Reviewed-by: Oswald Buddenhagen
|
| |\ \ \
| | | |/
| | |/| |
|
| | |\ \ |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
... as described in the documentation. Furthermore:
* use qt_safe_select to timeout correctly
* return immediately when timeout value is 0
Reviewed-by: Oswald Buddenhagen
|
| | |\ \ \
| | | | |/
| | | |/| |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This fixes a timeout that occurred on Mac with the gui event dispatcher:
we were waiting for a write notification, but timed out when we were in
closing state and still waiting for the socket engine to complete
writing.
Now we close the socket anyway after 2 seconds.
Reviewed-by: Thiago Macieira
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
only disconnect from host when all bytes have been written; i.e. not
only check whether the write buffer is empty, but also check whether
the socket engine has still bytes to write. This is necessary for
HTTP and SOCKS5 socket engine, because they both contain an inner TCP
socket which also does buffering. For the native socket engine, there
is no difference with this patch.
Reviewed-by: Markus Goetz
Reviewed-by: Thiago Macieira
|
|/ / / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
the indexOf() call did not consider actualReadBufferSize and thus
scanned uninitialized memory for newlines.
Reviewed-by: phartman
|
| |_|/
|/| |
| | |
| | |
| | |
| | | |
However, compiling with QT_NO_ICON will still not work :(
Reviewed-by: tom
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
I suspect because of missing quotation marks those strings were not
showing up. Also, wrapping QT_TRANSLATE_NOOP inside a tr() call
makes no sense. Also changed the class from QObject to QSslSocket.
Task-number: QTBUG-5059
Reviewed-by: ossi
|
| |/
|/|
| |
| |
| | |
Task-number: QTBUG-4984
Reviewed-by: Thiago
|
|/
|
|
| |
Reviewed-by: Thiago
|
|
|
|
|
|
|
|
| |
QHttp is deprecated, but let's be nice and fix this.
POST/PUT now properly works over HTTPS without
buffering the whole data when it is not needed.
Reviewed-by: Peter Hartmann
|
|
|
|
|
|
|
|
|
| |
In certain cases a SSL transfer stalled when a readBufferSize was set.
This change triggers a SSL transmission when there is data on the
socket waiting to be decrypted.
Task-number: QTBUG-3860
Reviewed-by: Thiago
|
|
|
|
|
|
|
| |
Handle setSocketOption and forward it to the plainSocket that
QSslSocket is using internally.
Reviewed-by: Thiago
|
|\
| |
| |
| |
| | |
Conflicts:
src/gui/egl/qegl_symbian.cpp
|
| |
| |
| |
| |
| | |
Task-number: Salesforce 00062670
Reviewed-by: Thiago
|
| |
| |
| |
| |
| |
| |
| |
| | |
Backport af71faf8cb2c9cbf34c408b81ce7ae1ef6c6403e from 4.6 to
4.5.
Task-number: 261999
Reviewed-by: Peter Hartmann
|
| |
| |
| |
| |
| | |
Task-number: 262144
Reviewed-by: TrustMe
|
| |
| |
| |
| |
| |
| | |
Clarify about bytesWritten() and encryptedBytesWritten()
Reviewed-by: David Boddie
|
| |
| |
| |
| |
| |
| | |
... not only on bytesWritten()
Reviewed-by: Peter Hartmann
|
| |
| |
| |
| | |
Reviewed-by: Peter Hartmann
|