multiple_choices vs multiple_choices_redirect #184

Activity

1. Nikhil172913832 commented on Jan 1, 2026

   

   Nikhil172913832

   on Jan 1, 2026

   More actions

   I dug a bit deeper and was able to confirm @sk1p ’s findings. The test currently hits /multiple_choices_redirect, which isn’t defined in SimpleApp and falls back to call, returning a 200 with Cache-Control: max-age=5000, so the test passes without actually exercising a 300 response. The /multiple_choices endpoint does return a 300, but without explicit freshness information, and while 300 responses are cacheable by default, CacheControl doesn’t apply heuristic freshness, so a response without explicit cache headers won’t be reused. Based on that, a possible fix would be to correct the test URL to /multiple_choices and add an explicit Cache-Control header to that endpoint, which should make the test deterministic and closer to its original intent. I might be missing something here and would appreciate any thoughts.