mirror of
https://github.com/wiremock/WireMock.Net.git
synced 2026-01-11 21:10:32 +01:00
Response with 500 status code is very slow
#482
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @HappyRashair on GitHub (Jan 17, 2023).
Originally assigned to: @StefH on GitHub.
Describe the bug
Response with
500response is significantly slower than corresponding400responseExpected behavior:
Performance should be roughly the same
Test to reproduce
Other related info
.NET: Core 3.1
.Xunit: 2.4.1,
WireMock.Net: 1.5.5
@StefH commented on GitHub (Feb 6, 2023):
@HappyRashair
I did add that example code to https://github.com/WireMock-Net/WireMock.Net/pull/882
And when calling WireMock.Net from postman, the response for 400 and 500 is quick.

So can you please double check your application?
@HappyRashair commented on GitHub (Feb 7, 2023):
Behaviour in our code is not different whether it's 400 or 500.
I've tested it again and it makes a different with / without the guid as path - perhaps it's something with longer paths matching?
It's fast in postman as you noticed - the issue occurs when I run it in the IDE (Rider in my case)
@StefH commented on GitHub (Feb 18, 2023):
I'm closing this issue because it's very difficult for me to reproduce. If you can reproduce it with an console-app or example project, please comment here or create a new issue.