Hi Nicolas
I've seen a similar issue on v4.0 /IIS7.5. It is hard to tell what caused it, likely an update to either .NET framework or IIS which cased it to change the standard asp.net api behaviour. Upgrading to a newer version has solved the problem, so I would recommend to do so as well. Note that Composite C1 v4.1 and newer require .NET 4.5
I've seen a similar issue on v4.0 /IIS7.5. It is hard to tell what caused it, likely an update to either .NET framework or IIS which cased it to change the standard asp.net api behaviour. Upgrading to a newer version has solved the problem, so I would recommend to do so as well. Note that Composite C1 v4.1 and newer require .NET 4.5