@santhoshm687661can you please provide the Request Progress Log for this request? This should help shed quite a bit of light of what's going on - ex. does it stop processing at the CORS filter, or some other Filter, or is it resolving to the incorrect servlet, etc.
There is no known issue with any version of AEM that turns non-204 responses to 204 responses. I understand that this used to work pre-upgrade and doesn't now - but you'll have to help w/ the investigation if you want to pinpoint and resolve the problem - else we're all just taking guesses 🙂
@santhoshm687661 Note that the UI says it shows a maximum of 20 requests at a time. So here's what you need to do (and do these steps in rapid succession).
1. Tap the clear button on the Requests console (top right)
2. Trigger a POST to the end-point
3. Refresh the Requests console page
4. Click on the POST to the end-point
If this is a local instance, you can also use AEM Chrome Plugin to capture this data on a per-request basis (its actually immensely hands for development, IMO)