Single Host with Multiple Ports

[naiveZhou]

Hello, I have reproduced a bug on my side.The first time I access http://127.0.0.1:9000, it works normally. However, after I visit http:////127.0.0.1:9001/swagger , when I go back to access http://127.0.0.1:9000 again, it returns a 404 error. Repeated accesses will result in abnormal behavior.I'm wondering if this might be caused by a backend caching issue. Could you please help look into it? I already know that the ServeStaticFiles method is not being invoked during the second access, but I have no idea why this is happening.
I have tried using the single-port mode on my side, but during registration, the use of Route.AnyPath will cause a conflict on startup and prevent the service from running properly.

Looking forward to your reply. Thank you!
SiskWithSwaggerDemo.zip

[CypherPotato]

Hello! Thanks for reporting.

Indeed, it was a bug in the abstraction of the HttpListener Engine. For some reason, I was lazily loading a shared instance of HttpListenerAbstractEngine, which was sharing the ListeningHosts for the two instances.

I fixed it in this commit and released version v1.6.1 with this fix.

Please report any other bugs you find. Thanks!

[naiveZhou]

Thanks a lot for your solution! It works perfectly, really appreciate it