Open tekhedd opened 9 years ago
Is this for self hosting without OWIN?
Could we just drop support for non-owin based self hosting?
This is for self-hosting, but in any situation where the stream is copied to a memorystream, the incoming RequestStream's input stream is not closed, as it should be, so I would see this as a bug in all situations.
Are you suggesting that your first instinct when fixing a bug I reported that I found while implementing non-OWIN based SelfHosting in my app is to drop support? Awesome. :} I'm feeling great about my decision to use Nancy in this project.
@tekhedd no. I'm suggesting dropping support for self hosting in Nancy in favour of Owin self hosting which doesn't suffer from this problem. I personally don't know anyone not using non-owin self hosting now-a-days. The old self hosting has other issues besides the one you have raised.
Is there any reason why you can't use the owin host?
1) I'm running cross platform here. A stable, widely used OWIN implementation that runs on Mono... would be...which one again?
2) I personally don't know anyone who watches soccer. Why do they keep broadcasting it on the TV?
Katana is both widely used and stable. What's the problem on Mono?
MoveToWritableStream() does not close the old stream after copying it to memory. This leaves HttpListenerRequest's stream unclosed when self-hosting.