Details
-
User Story
-
Resolution: Done
-
P2: Important
-
6.x
-
None
-
-
8
-
Team Two Foundation Sprint 50, Team Two Foundation Sprint 51, Team Two Foundation Sprint 52
Description
As a PO I would like to know what is missing or incomplete on the implementation side of the current "Lightweight HTTP server". I see two stages of completing it:
1) Are use cases clear and know so that we can agree on the a feature scope (some use cases are mentioned in https://www.qt.io/blog/2019/01/25/introducing-qt-http-server)
2) What is missing in this feature scope
3) Known bugs in the current implementation
4) What is needed to be done to make it a module in Qt
Source location: https://code.qt.io/cgit/qt-extensions/qthttpserver.git/
Attachments
Issue Links
- relates to
-
QTBUG-60109 HTTP server user authentication
- Open
-
QTBUG-75087 Basic protection against DDoS, flooding, brute-force
- In Progress
-
QTBUG-75084 Document how to implement basic HTTP authentication
- Closed
-
QTBUG-75086 Configurable logging
- Closed
-
QTBUG-75081 Improve the implementation of concurrent processing in the Qt HTTP server and document it
- Closed
-
QTBUG-75078 Ensure compiance with HTTP 1.1 for the Qt HTTP server
- Withdrawn
- resulted in
-
QTBUG-100533 QtHttpServer: Missing socket error handling in QSslServer
- Closed
-
QTBUG-100476 QtHttpServer: fix QtConcurrent usage
- Closed
-
QTBUG-100478 QtHttpServer: reorganize branching and get rid of compat code in dev
- Closed
-
QTBUG-100479 QtHttpServer: Fix failing SSL auto tests
- Closed
-
QTBUG-100994 Add qthttpserver to qt5
- Closed
-
QTBUG-100481 QtHttpServer: Add module documentation
- Closed
-
QTBUG-100487 QtHttpServer: Consider using Qt's HTTP header parser code instead of unmaintained 3rd party project
- Closed
-
QTBUG-100660 QtHttpServer: Build and test the package in CI
- Closed
-
QTBUG-100868 QtHttpServer: API/ABI review and modernization
- Closed
-
QTBUG-100823 Move QSslServer from QtHttpServer and QtWebSockets into QtNetwork
- Closed