-
-
Notifications
You must be signed in to change notification settings - Fork 204
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Proxy mode: Incorrect handling of multipart requests #468
Labels
Comments
Bug is confirmed, thanks for analyzing. However fixing will take some time... |
You are welcome. Yeah, fix will not be trivial, especially bearing in mind different target frameworks. |
@LevYas Can you try version |
@StefH - you are incredibly fast. I've just tested - it works! |
You are a very good tester! I will make new official version today. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have an ASP.Net Core API method with the following signature
I call this method from Postman or curl or from my front-end with a small picture file. It's ok without proxy, but with proxy file is always null.
It looks like WireMock.Net treats multipart requests as a single part request with raw data, but I can be wrong. I added reading the
![2020-05-17 14_34_07-WireMock Net Solution (Debugging) - Microsoft Visual Studio](https://user-images.githubusercontent.com/36070899/82152438-ce65fd80-9869-11ea-9d01-d424a876d2f5.png)
Form
field and it contains the right content:I created a repro here https://github.com/LevYas/WireMockNetRepro
The text was updated successfully, but these errors were encountered: