| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
Source code that includes <QNetworkCookieJar> implicitly includes
QNetworkCookie in Qt 4.5. Restore this and keep Qt compiling after
the split up by including qnetworkcookie.h from qnetworkcookiejar.h
Reviewed-by: Trust me
|
|
|
|
| |
Reviewed-by: Trust Me
|
|
|
|
|
|
|
|
| |
Factor our the Channel object to a new file. My goal is to
make QHttpNetworkConnection more maintainable before
implementing HTTP pipelining.
Reviewed-by: Peter Hartmann
|
|
|
|
|
|
|
|
|
|
|
| |
into qnetworkcookiejar[h,_p.h,cpp].
one adjustment was necessary from the merge request:
The line 110 in qnetworkcookie.h needed to include
qnetworkcookiejar.h, not <QtNetwork/QNetworkCookieJar> .
Merge-request: 1015
Reviewed-by: Peter Hartmann
|
|
|
|
|
|
|
| |
The comment was speaking about upload progress, however the code
is about download progress.
Reviewed-by: TrustMe
|
| |
|
|
|
|
| |
Reviewed-by: Thiago
|
|
|
|
| |
Reviewed-by: Thiago
|
|
|
|
|
|
|
|
|
|
|
|
| |
the same method was also added to QSslSocket.
previously, it was only possible to ignore all SSL errors; now, it is
also possible to only ignore specific SSL errors, given by a QList of
QSslErrors.
Moreover, it is possible to call this newly added method right after
connecting, not just when we get the SSL error.
Reviewed-by: Thiago
Task-number: 257322
|
|\
| |
| |
| |
| |
| | |
Conflicts:
src/gui/graphicsview/qgraphicsscene.cpp
src/gui/kernel/qt_cocoa_helpers_mac_p.h
|
| |
| |
| |
| | |
Reviewed-by: TrustMe
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Properly load the raw headers and properly handle the redirection
when having a network cache in AlwaysCache mode (equals the offline
mode in web browser).
Task-number: 256240
Reviewed-by: Thiago Macieira
|
| |
| |
| |
| | |
Also marked the other QHttpXxx classes as \obsolete.
|
| |
| |
| |
| | |
The base function was \internal pr private.
|
|\ \
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
src/3rdparty/webkit/VERSION
src/3rdparty/webkit/WebCore/ChangeLog
src/3rdparty/webkit/WebCore/generated/JSDOMWindow.cpp
src/3rdparty/webkit/WebCore/page/DOMWindow.idl
src/corelib/io/qdiriterator.cpp
src/plugins/gfxdrivers/directfb/qdirectfbpaintengine.cpp
src/plugins/gfxdrivers/directfb/qdirectfbpixmap.h
tests/auto/qxmlquery/tst_qxmlquery.cpp
tools/linguist/lconvert/main.cpp
|
| |
| |
| |
| | |
Reviewed-by: TrustMe
|
| |
| |
| |
| | |
Reviewed-by: Thiago
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Better usage of move semantics with implicit sharing to avoid
detaching (=malloc/memcpy). Also some other improvements.
Download performance improvement is around 20% according
to the httpDownloadPerformance autotest.
Reviewed-by: Thiago Macieira
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
The isFinished() method will return true if the reply has successfully
finished or has been aborted.
Task-number: 257349
Reviewed-by: Thiago Macieira
|
|\ \
| |/
| |
| |
| |
| | |
Conflicts:
src/network/access/qnetworkaccesshttpbackend.cpp
src/network/access/qnetworkreplyimpl.cpp
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In some cases, weird timing issues could occur. In those cases, an EOF
was sent twice for the upload data, leading to the HTTP code being
confused and sending the request headers twice.
Task-number: 257662
Reviewed-by: Thiago Macieira
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
It is possible that finished() function will be called several times,
for example if the user calls QNetworkReply::close() as a result of
the authenticationRequired() signal, the connection will be closed
(which results in emitting a finished() signal), and then the
authentication will be cancelled, which will also try to emit the same
signal, however the connection state will already be set to Finished.
The fix is to just make sure if the finished() signal has already been
emitted by checking if the connection state is not Finished or
Aborted.
Reviewed-by: Thiago Macieira
|
| |
| |
| |
| |
| |
| | |
Cache return value of expensive function.
Reviewed-by: Peter Hartmann
|
| |
| |
| |
| |
| |
| |
| | |
Directly put a QRingBuffer from one QRingBuffer to
another QRingBuffer.
Reviewed-by: Thiago Macieira
|
|\ \
| |/ |
|
| |
| |
| |
| |
| |
| | |
A few "fixes" to make that number go down..
Reviewed-by: Thiago Macieira
|
| |
| |
| |
| |
| |
| |
| | |
Use the QRingBuffer properly when reading known-size, non-chunked,
non-compressed data from HTTP.
Reviewed-by: Thiago Macieira
|
|\ \
| |/
| |
| |
| |
| |
| | |
Conflicts:
src/3rdparty/webkit/VERSION
src/3rdparty/webkit/WebCore/ChangeLog
src/network/access/qnetworkreplyimpl.cpp
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This fixes a bug that occured together with a QProgressDialog.
The signal emission was like:
readyRead readyRead readyRead [...] readyRead finished readyRead
Now finished should be properly at the ending of this sequence.
Task-number: 256630
Reviewed-by: Thiago Macieira <thiago.macieira@nokia.com>
|
| |
| |
| |
| |
| |
| | |
Change the QByteArray to a QRingBuffer to save re-allocation time.
Reviewed-by: Thiago Macieira <thiago.macieira@nokia.com>
|
| |
| |
| |
| |
| |
| |
| |
| | |
Uncluttered and duplicated some function to make it more clear
what is happening. Was a bit confusing before if compressed data
or uncompressed data is handled.
Reviewed-by: Peter Hartmann
|
| |
| |
| |
| | |
Reviewed-by: Peter Hartmann
|
| |
| |
| |
| |
| |
| |
| |
| | |
should make it easier to apply a network disk cache with code snippets
now
Reviewed-by: David Boddie <dboddie@trolltech.com>
Reviewed-by: Martin Petersson <martin.petersson@trolltech.com>
|
|\ \
| |/ |
|
| |
| |
| |
| | |
Reviewed-by: Volker Hilsheimer
|
|\ \
| |/
| |
| |
| |
| |
| | |
Conflicts:
configure.exe
tests/auto/qpainter/tst_qpainter.cpp
translations/qt_ru.ts
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This makes sure the keep-alive connections stay open even
if someone deletes a QNetworkReply which will then go all the
way down to removeReply(QHttpNetworkReply).
Should fix
http://lists.trolltech.com/pipermail/qt-interest/2009-June/007777.html
Reviewed-by: Peter Hartmann
|
| |
| |
| |
| |
| |
| |
| | |
Renamed some classes and member variables.
Their names were causing confusion before because.
Reviewed-by: Peter Hartmann
|
| |
| |
| |
| | |
I mixed this up several times before, so here is the comment for it.
|
| |
| |
| |
| |
| |
| |
| | |
This stops QNetworkAccessManager from loading the OpenSSL libs,
certificates etc. when they are not needed for the non-HTTPS case.
Reviewed-by: mariusSO
|
|\ \
| |/ |
|
| |
| |
| |
| | |
Reviewed-by: Trust Me
|
| |
| |
| |
| |
| |
| |
| | |
This should better communicate that new applications should
use QNetworkAccessManager.
Reviewed-by: David Boddie
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Even though the standard mandates a maximum of 2 connections, most
new browsers support atleast 6 connections. So we are also bumping the
limit.
Task-number: 251144
Reviewed-by: Markus Goetz
Reviewed-by: Peter Hartmann
|
| | |
|
| |
| |
| |
| | |
Reviewed-by: Prasanth
|
| |
| |
| |
| | |
Reviewed-by: trustMe
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
added new method QNetworkAccessManager::deleteResource (naming the
method "delete" was not possible since it is a reserverd word in
C++) and adjusted all the internals necessary.
Task-number: 242916
Reviewed-by: Thiago
|