[Vtigercrm-developers] BUG: Maximum data limit in New Quote due to Transport Mechanism

[Sergio A. Kessler]

according to the http standard:

- all things that modify information (insert, update) should be made
with POST, not with GET.

- all things that do NOT modify information (select, view), should be
made with GET.

to solve the problem that some variables can be seen in the url bar
(and you do not like that), I just simply encrypt and base64'd all the
params... so you see a lot of garbage in the url

/sak


On 1/18/06, Dennis Grant <dgrant at accuratetechnologies.com> wrote:
>
>
>
> Urk,
>
>
>
> I just had a user stumble across a rather insidious bug in creating/editing
> a Quote.
>
>
>
> Quotes have two LONGTEXT fields – DESCRIPTION and TERMS AND CONDITIONS –
> that they can fill in with arbitrary text. This is Sweet Crunchy Goodness,
> as that ability meshes very well with our Quote generation paradigm.
>
>
>
> However, it appears that the transport mechanism for submitting a new Quote
> is GET, not POST – meaning that all the data filled in in these two text
> fields are placed on the URL line, for which there is a maximum size.
>
>
>
> The symptom if the bug is that attempting to submit a Quote which contains
> more data than is allowed (put a lot of text in one or both text boxes)
> fails quietly – no error message, no nothing. Delete enough of the data out
> of the textbox to drop the size of the GET below this maximum, and
> everything works as normal.
>
>
>
> This is on the default install of vTiger that comes with Apache, MySQL, etc
> as one giant tarball.
>
>
>
> Should the transport mechanism in vTiger be changed to POST? What are the
> consequences of doing this?
>
>
>
> Is there someone at vTiger who will take up this bug? It is a showstopper
> for us.
>
>
>
> DG
> _______________________________________________
> vtigercrm-developers mailing list
> vtigercrm-developers at lists.vtigercrm.com
> http://lists.vtigercrm.com/mailman/listinfo/vtigercrm-developers
>
>
>