Hi Daniel,
My understanding (and I may be wrong) is that when using HTTP.SYS you register to handle only a particular URL (or set or URLs). If people are probing port 80 randomly, there is no way they will know your URL, it does not even get to your application and windows will do whatever it does with port 80 probes. Just ignore them or whatever. I dont know why I would need to monitor port 80 traffic that is not directed at my application. I wont even know it exists.
That being said, in the scenario I envision, it will be used within a university and only available by computers within the university. So there may be random port scanning going on in the university, but it would be much less than if this was a public machine.
Except I only get 1 app per computer, minus any shenanigans with playing with IP address etc.
My understanding (and I may be wrong) is that when using HTTP.SYS you register to handle only a particular URL (or set or URLs). If people are probing port 80 randomly, there is no way they will know your URL, it does not even get to your application and windows will do whatever it does with port 80 probes. Just ignore them or whatever. I dont know why I would need to monitor port 80 traffic that is not directed at my application. I wont even know it exists.
That being said, in the scenario I envision, it will be used within a university and only available by computers within the university. So there may be random port scanning going on in the university, but it would be much less than if this was a public machine.
(03-22-2018, 08:45 PM)kudzu Wrote: With IntraWeb Standalone, you ship a single EXE. They run that exe /install, start the service. Done. Doesn't get simpler than tha.
Except I only get 1 app per computer, minus any shenanigans with playing with IP address etc.