Skip to content

Don't send extraneous '0\r\n\r\n' with non-chunked HTTP/1.0#24518

Merged
arendst merged 3 commits intoarendst:developmentfrom
s-hadinger:tasmota_webserver_fix_non_chunked
Mar 3, 2026
Merged

Don't send extraneous '0\r\n\r\n' with non-chunked HTTP/1.0#24518
arendst merged 3 commits intoarendst:developmentfrom
s-hadinger:tasmota_webserver_fix_non_chunked

Conversation

@s-hadinger
Copy link
Copy Markdown
Collaborator

Description:

Create a new class TasmotaWebServer to unify and expand ESP8266WebServer (ESP8266) and WebServer (ESP32). This makes a cleaner abstraction than the current ESP8266WebServer wrapper.

Fixes the extraneous 0\r\n\r\n with non-chunked HTTP/1.0

Related issue (if applicable): fixes #24508

Checklist:

  • The pull request is done against the latest development branch
  • Only relevant files were touched
  • Only one feature/fix was added per PR and the code change compiles without warnings
  • The code change is tested and works with Tasmota core ESP8266 V.2.7.8
  • The code change is tested and works with Tasmota core ESP32 V.3.1.10
  • I accept the CLA.

NOTE: The code change must pass CI tests. Your PR cannot be merged unless tests pass

@s-hadinger
Copy link
Copy Markdown
Collaborator Author

@arendst Are you ok with this change?

@arendst arendst merged commit 6c8fc7e into arendst:development Mar 3, 2026
64 checks passed
@arendst
Copy link
Copy Markdown
Owner

arendst commented Mar 3, 2026

Thx

josef109 pushed a commit to josef109/Tasmota that referenced this pull request Mar 15, 2026
…24518)

* Don't send extraneous '0\r\n\r\n' with non-chunked HTTP/1.0

* Fix compilation

* Fix compilation
Jason2866 added a commit that referenced this pull request Mar 18, 2026
…asmotaWebServer (#24568)

* Change Webserver type from ESP8266WebServer to TasmotaWebServer
* Cast webcam resolution to int32_t in WcSetup calls
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Extraneous bytes after body of HTTP/1.0 response

2 participants