search

lnobad / lidgren-network-gen3

Automatically exported from code.google.com/p/lidgren-network-gen3
0 stars 0 forks source link

UPnP failures #153

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Perform UPnP discovery from behind a proxy that requires authentication 
(happens running the test project with UPnP enabled)

What is the expected output? What do you see instead?
I would expect NetPeer.Internal.cs to drop common error responses, I see 
messages about Malformed Packets (407 errors from my particular proxy server 
are reading as payload length 1514, but only contain ~220-225 bytes)

What version of the product are you using? On what operating system?
r340; Windows XP

Please provide any additional information below.
Workaround is to add common message handling in the try/catch block of the upnp 
handler in NetPeer.Internal.cs and perform a return instead of continuing to 
process the message

May be specific to some proxy servers incorrectly reporting their lengths.

Original issue reported on code.google.com by Sag...@gmail.com on 22 Aug 2013 at 6:24

GoogleCodeExporter commented 9 years ago 
Better late than never; should be fixed in rev 383

Original comment by lidg...@gmail.com on 10 Oct 2014 at 3:56