Timeline for Why HTTPSReciever maxSize attribute default value is 10MB?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 22, 2013 at 6:10 | vote | accept | AlokBhatt | ||
| Aug 21, 2013 at 16:52 | comment | added | Ram G | The default could be higher but traditionally this has been on par with IIS default values in IIS 6 default is 20MB, IIS7 default is 30MB. Rationale could be, it is 10MB is to keep the value less than IIS defaults as well backwards compatibility. Note, just changing this number to higher value is not just sufficient and you also need to increase the web server default sizes (IIS 7 - 30MB) as well. | |
| Aug 21, 2013 at 16:31 | comment | added | AlokBhatt | @Ram that is right that it can be a design flaw. But the issue a very common issue. So i discussed | |
| Aug 21, 2013 at 13:25 | comment | added | Ram G | 100 components on a Page is not ideal or at least in my experience. It is unmanageable for authors and there is some fundamental design flaw (at least in my PoV). | |
| Aug 21, 2013 at 13:03 | comment | added | AlokBhatt | I was thinking of a case where 100 components existing on a page with 3 multimedia link field. If image size sums to 0.5 MB per component then the package size will be nearly 55-60 MB. So 100 MB seems to be fine in such a scenario. But I questioned about max size because if number of component start attached on this page increase to 500 or 1000. | |
| Aug 21, 2013 at 12:09 | history | answered | Nuno Linhares♦ | CC BY-SA 3.0 |