In the course of debugging my p:http-request step and discussing the various test outcomes with @xml-project, the following observation was made:
If a request produces no documents, it's impossible to tell what the final URI was. In particular, consider the case where you've set follow-redirect to 2 but the request redirects more than twice. There's no output so there's no document from which you can get the base URI, so there's no way to know what the last redirect location was.
The simple fix seems to be to add this information to the report output. It seems reasonable, it's trivial to implement, and it does mean pipeline authors can rely on reading the value irrespective of whether or not a document was produced.
In the course of debugging my
p:http-requeststep and discussing the various test outcomes with @xml-project, the following observation was made:If a request produces no documents, it's impossible to tell what the final URI was. In particular, consider the case where you've set
follow-redirectto 2 but the request redirects more than twice. There's no output so there's no document from which you can get the base URI, so there's no way to know what the last redirect location was.The simple fix seems to be to add this information to the
reportoutput. It seems reasonable, it's trivial to implement, and it does mean pipeline authors can rely on reading the value irrespective of whether or not a document was produced.