Store HTTP response strings in PROGMEM on ESP8266 #372
+107
−87
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mathieucarbou
approved these changes
Jan 22, 2026
mathieucarbou
force-pushed
the
response_strings_flash_esp8266
branch
from
e83943d to
a6649d3
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Moves HTTP response code strings (e.g., "OK", "Not Found", "Internal Server Error") to flash memory on ESP8266, saving ~700 bytes of RAM.
literals.h:DECLARE_STR- stores strings in PROGMEM on ESP8266, constexpr elsewhereSTR- returns__FlashStringHelper*on ESP8266,const char*elsewhereSTR_RETURN_TYPE- platform-appropriate return typeresponseCodeToString()to use these macrosESP8266 has only ~45KB usable RAM. These strings were consuming RAM unnecessarily when they could be stored in flash and accessed via PROGMEM.