Request/Header/Path/Query String Length

[ncorn]

I think we need definitive rules on lengths:

1. Request Size
2. Path Size
3. Query string size

Andrew has pointed out that a lot of different frameworks and servers slice and dice those limits in a lot of different ways. My primary concern is the following scenario:

• A customer wants to do a filter excluding a list of values. That list includes 5K IDs. At most the query string length in IIS will allow is 4K. Making the desired filter impossible in the system.

Overall statement being that if we rely on the query string for filtering exclusively we need to define its max usage so that we have defined what use cases it has solved or not solved.

[dougwilson]

The main benefit, I think, for stating this is that when evaluating a new proxy or server software, we can go "will, does it handle a path of 4000 octets?" and it's a good argument against choosing a particular serve software or an acknowledgement that a setting needs to be adjusted to abide by the REST guidelines.

[ncorn]

It would also allow us to give best practices on a variety of platform configurations. That would help newcomers know they are playing nice with the platform. Also allows us to develop a certification testing process.

[ncorn]

We agree that this needs to be done. It is slaed for 4.2. Work is in progress.