Skip to content

fix: improperly formed mime-type changed from binary to application/…#21

Merged
OlegDokuka merged 1 commit into
rsocket:masterfrom
aboccag:master
Sep 8, 2020
Merged

fix: improperly formed mime-type changed from binary to application/…#21
OlegDokuka merged 1 commit into
rsocket:masterfrom
aboccag:master

Conversation

@aboccag

@aboccag aboccag commented Sep 7, 2020

Copy link
Copy Markdown
Contributor

In case we do not use the LoopbackTransport, (either TCP or WS) we need to specify a default BINARYMIMETYPE
The previous was specified but incorrect.

@OlegDokuka OlegDokuka merged commit 47a86a6 into rsocket:master Sep 8, 2020
@OlegDokuka

Copy link
Copy Markdown
Member

@broadside74 thank you for your contribution!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Improperly formed default mime type causes connection error when connecting to spring-boot rsocket server

2 participants