fix: resolve security header profile persistence bug

Browse Source

- Add diagnostic logging to track security_header_profile_id conversions
- Replace silent failures with explicit HTTP 400 error responses
- Fix ProxyHostService.Update to properly handle nullable foreign keys
- Fix frontend dropdown to use explicit null checks (no falsy coercion)
- Add 7 comprehensive tests for profile assignment edge cases

Root cause: Backend handler had no else clause for type conversion failures,
causing old values to persist. Fixed by adding logging, error handling, and
changing service layer from Updates() to Select("*") for nullable FKs.

Refs: #<issue_number_if_applicable>

...

This commit is contained in:

GitHub Actions

2025-12-18 23:45:42 +00:00

parent 555ab5e669

commit 1513c0b636

7 changed files with 1396 additions and 1032 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download Patch File Download Diff File Expand all files Collapse all files

docs/plans/current_spec.md

+463 -748

File diff suppressed because it is too large Load Diff