Carry hidden-field context through a redirect
Keep redirect destinations under your control and forward only the context the destination needs.
Select a screenshot to enlarge it.
Steps
- Define and test the source hidden field and identify the exact parameter expected by the destination.
Definitions identify the fields expected in the respondent URL. Supply harmless URL-encoded values when testing. - Inspect the ending action: the current REDIRECT_TO selector chooses END OF FORM or SCREEN OUT and does not expose a direct URL field. Confirm the supported destination-URL configuration before attempting to forward a value.
The current action selects an ending; this selector does not provide a direct destination-URL field. - Only use a supported destination-URL field and its own recall mechanism if offered. Do not substitute the hidden-field value into the hostname or infer URL recall support from the question-text picker.
- Test ordinary text, spaces, an empty value, and a value containing & to confirm correct encoding.
- Validate the received value at the destination and provide a sensible missing-value fallback.
Check before you rely on it
Treat all hidden-field values as untrusted. Forwarding a link parameter does not make it safe or verified.
If you need help
Use a fixed destination when the current editor cannot reliably recall and encode values.
Contact support with the relevant screen, time, and a redacted description. Keep credentials and private respondent information out of screenshots.