Pil0tXia opened a new issue, #4335:
URL: https://github.com/apache/eventmesh/issues/4335

   ### Search before asking
   
   - [X] I had searched in the 
[issues](https://github.com/apache/eventmesh/issues?q=is%3Aissue) and found no 
similar issues.
   
   
   ### Enhancement Request
   
   Most of the services that use `HandlerService` are affected by this bug. 
When sending webhook payloads using Postman and spoofing the hash value, the 
CloudEvent is sent successfully. However, Postman remains in a waiting state 
even after receiving a 200 or 500 status code. 
   
   Webhook Delivery Error:
   
   
![image](https://github.com/apache/eventmesh/assets/41445332/dcf095ed-b0d3-4ffd-ac8c-81d9f8bc0067)
   
   
![image](https://github.com/apache/eventmesh/assets/41445332/00be5240-ea5a-4e8b-aeb4-9bce1e314ed4)
   
   In the screenshots of the webhook documentation, the tasks are also failing: 
   
   
![image](https://github.com/apache/eventmesh/assets/41445332/642e0d1b-38da-4879-af0f-7a0547af0c01)
   
   
   ### Describe the solution you'd like
   
   After promptly closing the connection, Postman no longer waits, and the 
GitHub task succeeds.
   
   
![image](https://github.com/apache/eventmesh/assets/41445332/4f6c12d6-d7c8-46c2-88ec-c3af51feee43)
   
   
![image](https://github.com/apache/eventmesh/assets/41445332/b450112b-f6df-4fe6-9e13-73f95f5256c6)
   
   
   ### Are you willing to submit PR?
   
   - [X] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct) *


-- 
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]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to