Content-Type error message causes upnp devices to fail

Open
#61 8 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
45/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Stale
Tech stack
csharp
Domain
networking

Research direction

Inspect websocket-sharp/Net/HttpListenerRequest.cs around line 528, where the Content-Type error is produced. Reproduce the issue with a UPnP device or the reported case, then verify that the error message no longer includes the \r\n after the closing quotes and that affected devices can proceed.

Written by the indexing model from the issue text.

Description

https://github.com/sta/websocket-sharp/blob/master/websocket-sharp/Net/HttpListenerRequest.cs#L528

Tested with bubble upnp, and many others. See attached image. It's due to the \r\n after the double quotes.

untitled1

Dominant language
C#
Stars
6.1k
Forks
1.7k
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from sta/websocket-sharp

All issues in sta/websocket-sharp

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.