|
|
|
|
|
by itopaloglu83
198 days ago
|
|
Okay, I’m a little confused, the HTTP already supports 8000 octets, and some are having issues because they have too many filters? Looking at the logs I see that most of the long URI traffic is due to UTM and other tracking related codes, which are mainly a way to work around 3rd party cookie blocks. I must be missing something, because it sounds like to goal is to have longer URI without the need for encoding URL parameters, but without using POST. |
|
Suppose you have one filter but it has a few hundred twenty-character values.