Skip to content
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

Unsupported content type in HttpMessageDecoder #62

Closed
PhonicUK opened this issue Jan 4, 2016 · 1 comment
Closed

Unsupported content type in HttpMessageDecoder #62

PhonicUK opened this issue Jan 4, 2016 · 1 comment

Comments

@PhonicUK
Copy link

PhonicUK commented Jan 4, 2016

Griffin.Net.Protocols.Http.BadRequestException: Unsupported content-type: text/plain                                  
   at Griffin.Net.Protocols.Http.HttpMessageDecoder.TriggerMessageReceived (Griffin.Net.Protocols.Http.HttpMessage message) in <filename unknown>:line 0                                                                                   
   at Griffin.Net.Protocols.Http.HttpMessageDecoder.ProcessReadBytes (ISocketBuffer buffer) in <filename unknown>:line 0                                                                                                                    
   at Griffin.Net.Channels.TcpChannel.OnReadCompleted (System.Object sender, System.Net.Sockets.SocketAsyncEventArgs e) in <filename unknown>:line 0      
jgauffin added a commit that referenced this issue Apr 6, 2016
@jgauffin
Copy link
Owner

jgauffin commented Apr 6, 2016

corrected. Now allows text/plain even if it's not supported by the messadedecoder.

@jgauffin jgauffin closed this as completed Apr 6, 2016
jgauffin added a commit that referenced this issue Apr 6, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants