-
Notifications
You must be signed in to change notification settings - Fork 378
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
Deserializing big xml request in version 1.0.0.0 #380
Comments
test for DigDes#380
@BorisVezhyk Try increase quotas in binding declaration passed to UseSoapEndpoint method. Like this: https://github.com/kotovaleksandr/SoapCore/blob/develop/src/SoapCore.Tests/Serialization/ServiceFixture.cs |
Of course, I tried to increase quota,
but it didn't help and exception only with .net core 3.0 and more |
@BorisVezhyk Whats text of exception? |
Exception appears when service tries to deserialize request |
(get latest version of PipeStream from https://github.com/AArnott/Nerdbank.Streams)
@BorisVezhyk Please check again on my fork |
While I will check it out, Could you tell me where the issue is? My service get request is right without exception but on client-side on void method exception:
This method has attribute one-way=true; and I tried to set my method |
yes, it's bug. Please, create one more issue:) |
check on my fork OneWay operations, should be works |
I checked all. Good job. Big xml request works and OneWay too! |
Okay, tomorrow i will publish the nuget package. |
I need to deserialize a big xml request from a client. For example, the client posts xml request to upload file (pdf or tif). He uses convert to base64 these files and sends it to a server.
There is no problem with deserialization on 0.9.9.6 such xml requests. After research code I found a place where appears the problem.
class SoapMessageEncoder
The first method invoke
In this place there is an incomplete reading of the stream because of this, an error will fall during deserialization because xml is not complete.
The text was updated successfully, but these errors were encountered: