ottobackwards edited a comment on pull request #5475: URL: https://github.com/apache/nifi/pull/5475#issuecomment-958276229
@kevdoran wrt url encoding, I can see how that would be a problem, you don't want to decode into a path. I *guess* just showing encoded names in there and leaving it to the flow ( scripted processor or something ) to do this would be OK. But, given that, why have this at all? `invokehttp.response.url` and the `invokehttp.request.url`, so the attributes have the information, you can do what you want downstream and handle all the edge cases etc that you like. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
