What is the likelihood of the Composite C1 dev team investigating and, if required, making the necessary changes to add-on path names?We typically try to adapt to whatever horrors the real world throw at us so we run optimally in as many environments as possible, but since this is a major change (or rather, small changes in a lot of places that require retesting) and this is the first incident we are aware of, we won't abort current tracks to fix this right now. Typically that change if we start seeing a more widespread pattern or a customer who pays for product warranty complains.
We will add a task on this though - this is one of those "endless support" situations we generally try to avoid.
Our packages are open source, so you (anyone) is welcome to fix these things and send us a pull request. See https://github.com/Orckestra/C1-Packages
Do you know of any IIS Request Filtering settings? I've tried searching for an answer, but I cannot find how/where to set the equivalent of the URL Scan AllowDotInPath=1 setting but in Request Filtering so I can override this at application level.I can't answer that - I'm not familiar with Microsoft URL Scan configuration.
Are there any other Add-On modules with launch page names similarly affected by dots in their paths? i.e. How many more problems with Add-On's am I likely to encounter?So far we have been using the Dot.Name.Folder strategy for C1 Packages that puts content in the ~/Composite folder. For free open source packages these seem to be affected https://github.com/Orckestra/C1-Packages/search?utf8=%E2%9C%93&q=\InstalledPackages\content\views&type=Code
If this is a problem likely to occur with other web hosts due to them also implementing URL Scanning, then surely this should be something Composite C1 should add into the System Requirements section of you website?If we see this becoming a reoccurring problem we would typically just take the time to fix this.
What is the likelihood of the Composite C1 dev team investigating and, if required, making the necessary changes to add-on path names?Very likely - we just need to a less burdened (or see someone in the community step up and fix this on github).