[
https://issues.apache.org/jira/browse/FINERACT-915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Vorburger updated FINERACT-915:
---------------------------------------
Fix Version/s: 1.4.0
> Add /echo debug API endpoint
> ----------------------------
>
> Key: FINERACT-915
> URL: https://issues.apache.org/jira/browse/FINERACT-915
> Project: Apache Fineract
> Issue Type: New Feature
> Reporter: Michael Vorburger
> Assignee: Michael Vorburger
> Priority: Major
> Fix For: 1.4.0
>
>
> To investigate a problem such as FINERACT-914, but perhaps also similar other
> ones like it in the future, it would be useful if Fineract out of the box
> included a simple /echo API, which would simply return all HTTP Headers
> received in a request - exactly like the application received it.
> Those headers may or may not be the same as those actually sent from the
> outside... intermediate HTTP proxies from anything like ISP's Caches, cloud
> providers, and Spring Boto Framework Filter classes could have intercepted
> and modified them.
> While this is obviously just a debug tool, I don't see the harm in just
> always including it by default in the Fineract WAR. If it's a simple echo,
> there should be no security implications that I am aware of.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
