11 Answer(s)
-
1
Hi,
can you provide the logs of the host?
Kind regards Nico
-
0
Logs for host https://files.fm/u/hjsjyqv3t
-
0
Hi,
can you provide the logs of the host?
Kind regards Nico
https://files.fm/u/hjsjyqv3t
-
0
It seems that the anti forergy validation failed due to the missing RequestVerificationToken header. Could you send a screenshot of the request headers the browser is sending to the api?
Also check if there is a cookie set named "XSRF-TOKEN".
-
0
It seems that the anti forergy validation failed due to the missing RequestVerificationToken header. Could you send a screenshot of the request headers the browser is sending to the api?
Also check if there is a cookie set named "XSRF-TOKEN".
Create (Post) and update (Put) and Get Work Fine
-
0
Do you use a reserve proxy like nginx or something else that might block delete requests currently?
-
0
It seems that the anti forergy validation failed due to the missing RequestVerificationToken header. Could you send a screenshot of the request headers the browser is sending to the api?
Also check if there is a cookie set named "XSRF-TOKEN".
Create (Post) and update (Put) and Get Work Fine
I just saw that you are hosting behind an IIS in the response headers. Please ensure that the IIS is configured correctly to allow the DELETE Http-Verb.
-
0
-
0
Could you provide logs once again now that the 405 is gone?
Also it would be good if you share the code of the page. I created a fresh project using with a test entity using abp suite and there is an error modal displayed and no redirections are made to the error page.
Another thing: did you override the default Error page?
-
0
Could you provide logs once again now that the 405 is gone?
log files https://files.fm/u/vqfvekueu
i made pure web .net core api for test Delete Verb
i will make new test with apb suite and test
-
0
As is see it from the logs there is a really strang behavior when the deletion endpoints get called:
- The deletion fails due to missing Antiforgery headers
- The application whould return a HttpStatus Code 400 (BadRequest)
- After that i see in the logs that the request is finished and the status code is changed to a redirection (302) to the error page, sadly no logs state why this redirect ist done. The api should not redirect to some error pages on errors.
Can you reproduce this behavior in debug mode? If so you can send me the project so i can deep dive into the project and look whats causing this.
E-Mail: kontakt@chrobyte.de