| Commit message (Collapse) | Author | Age | Files | Lines |
|\ |
|
| |
| |
| |
| | |
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
|
| |_|/
|/| |
| | |
| | |
| | |
| | | |
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
|
| |
| |
| |
| | |
Reviewed-by: Trust me
|
| |
| |
| |
| |
| |
| |
| |
| | |
Added setOriginatingObject() and originatingObject() to QNetworkRequest
that internally tracks the QObject using a QWeakPointer.
Reviewed-by: Lars Knoll
Rubberstamped-by: Thiago
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
If you try to resolve 10.3.4.6, you're probably going to get that it
doesn't exist. On some systems, getnameinfo will return the IP address
in string form (Linux, without NI_NAMEREQD). On some others, it will
fail (Mac, Windows).
So harmonise by gracefully handling the case in which getnameinfo
fails.
Possible behaviour change: we don't try the forward resolution any
more, after completing the reverse one.
Reviewed-by: Peter Hartmann <peter.hartmann@nokia.com>
|
| |
| |
| |
| | |
Requested-By: Volker Hilsheimer
|
| |
| |
| |
| |
| |
| | |
Explicit destructor was needed by compiler.
Reviewed-by: Thiago Macieira
|
| |
| |
| |
| |
| |
| | |
After 4.6 API review.
Reviewed-by: Volker Hilsheimer
|
| |
| |
| |
| |
| |
| | |
we were calling sk_pop_free from OpenSSL with a wrong signature.
Reviewed-by: Olivier Goffart
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
It turns out that if socket was signalized via exception fds
set, we should signalize only write notifier in the case where
both read and write notifiers exist.
If in this case we send signal to read notification socket will
prematurely be closed.
x#Reviewed-by: Janne Antilla
|
| |
| |
| |
| | |
Workaorund for SO_REUSEPORT / SO_REUSEADDR regression bug.
|
|\ \
| |/ |
|
| |
| |
| |
| |
| |
| |
| |
| | |
Send a header that we accept every language. Works around a bug in some
broken websites and is hopefully of no harm for us.
Task-number: QT-952
Reviewed-by: Thiago
|
| |
| |
| |
| |
| |
| | |
Note: Those messages are to be translated in Qt 4.6
for the first time.
Reviewed-by: Kent Hansen <khansen@trolltech.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
we need the date header to calculate the age of the page, although this
increases disk usage when using a QNetworkDiskCache. A solution to
reduce the disk access of QNetworkDiskCache will be considered for a
later version of Qt.
Reviewed-by: Markus Goetz
Reviewed-by: Aleksandar Sasha Babic
|
|\ \
| |/
| |
| |
| |
| |
| |
| |
| | |
Reviewed-by: Joao
Conflicts:
src/gui/graphicsview/qgraphicsview.cpp
src/gui/widgets/qspinbox.cpp
tests/auto/qgraphicsview/tst_qgraphicsview.cpp
|
| |
| |
| |
| | |
Task-number: QT-1683
|
| |
| |
| |
| |
| |
| |
| |
| | |
This fixes a crash that occured because aborted requests were
not properly removed from the channel.alreadyPipelinedRequests.
Task-number: QTBUG-4507
Reviewed-by: Peter Hartmann
|
| |
| |
| |
| |
| |
| | |
Fixes a memleak
Reviewed-by: Peter Hartmann
|
| |
| |
| |
| | |
Reviewed-by: Peter Hartmann <peter.hartmann@nokia.com>
|
| |
| |
| |
| |
| |
| |
| |
| | |
receiving the WSAEMSGSIZE error means we could not read all the data
because the buffer was too small, but still we should return the number
of bytes read and not return -1
Reviewed-by: Marius Storm-Olsen
|
|\ \
| |/
| |
| |
| |
| | |
Conflicts:
tests/auto/qhttpnetworkconnection/qhttpnetworkconnection.pro
tests/auto/qhttpnetworkreply/qhttpnetworkreply.pro
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Since 925912ebf552417306a5bd20fd986afda6a582be QNetworkReplyImplPrivate
no longer holds its own pointer to the network cache and relies on the
backend to get it. Since the cache is used in our call to finished, we
must reset the backend only after that.
This fixes a crash I was seeing in Arora...
Reviewed-by: Markus Goetz
Reviewed-by: Peter Hartmann
|
| |
| |
| |
| | |
Reviewed-by: Trust Me
|
| |
| |
| |
| |
| |
| |
| | |
If pipeClosed is true, then we've already emitted the
readChannelFinished signal. We must not do this in close() in that case.
Reviewed-by: ossi
|
| |
| |
| |
| |
| |
| |
| |
| | |
If we've detected a broken pipe and we have no more data in the
read buffer, then we return -1 to signal EOF.
Additionally, we close the QLocalSocket.
Reviewed-by: ossi
|
| |
| |
| |
| |
| |
| |
| | |
If we detect in a read operation that the pipe has been closed,
we must emit the readChannelFinished signal.
Reviewed-by: ossi
|