CLOUDCRUISE UNITED

PDF Case: Report Generated by Form POST

The report content comes from the POSTed fields. A GET of the same URL returns a different, valid PDF that says "No data found". A capture that re-fetches the URL instead of keeping the POST response lands the wrong file.

Form POST, same tab, Content-Disposition: inline

Form POST, target=_blank, Content-Disposition: inline

Form POST, same tab, no Content-Disposition header

Expected file:

  • Contains "Length of Stay: Maple Grove SNF"
  • Does not contain "No data found"
  • With a token query parameter, the third fetch of the URL returns 404