Skip to content

fix(fproxy): Preserve allowedHostsFullAccess on restart#1077

Merged
leumor merged 1 commit intorelease/2from
bugfix/fproxy-allowedhostsfullaccess-persist
Feb 23, 2026
Merged

fix(fproxy): Preserve allowedHostsFullAccess on restart#1077
leumor merged 1 commit intorelease/2from
bugfix/fproxy-allowedhostsfullaccess-persist

Conversation

@leumor
Copy link
Collaborator

@leumor leumor commented Feb 23, 2026

Summary

  • fix initialization order in SimpleToadletServer so allowedHostsFullAccess is read only after the option is registered
  • prevent fallback-to-default behavior from overwriting a user-configured fproxy.allowedHostsFullAccess on startup
  • add regression coverage in SimpleToadletServerTest to verify persistent-config value retention after finishedInitialization()

How To Test

  • run ./gradlew test --tests *SimpleToadletServerTest
  • run ./gradlew test
  • manual sanity check:
    1. stop node
    2. set fproxy.allowedHostsFullAccess in cryptad.ini to a non-default IP
    3. start node
    4. confirm value is preserved and not rewritten to loopback defaults

Register access options before reading allowedHostsFullAccess so persistent values are loaded instead of the missing-option fallback.

Add a regression test that seeds fproxy.allowedHostsFullAccess from PersistentConfig and verifies the value is retained after finishedInitialization().
@sonarqubecloud
Copy link

@leumor leumor merged commit d327296 into release/2 Feb 23, 2026
4 checks passed
@leumor leumor deleted the bugfix/fproxy-allowedhostsfullaccess-persist branch February 23, 2026 06:09
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.

1 participant