You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Today we encountered an issue with lengthy parameters data.
In one of our reports to KM we send one of the parameters we get on our API. At some point we started seing large timeouts. After some careful evaluation we found these on the logs:
<Mon Nov 19 12:29:12 2012> End of file reached for host trk.kissmetrics.com:80
Hey @joseairosa - I apologize for this delayed response. This is something I have brought up recently (the limits of GET vs. using a POST). We have worked this into our new REST API. I am going to shoot you an email with some more details.
Hi,
Today we encountered an issue with lengthy parameters data.
In one of our reports to KM we send one of the parameters we get on our API. At some point we started seing large timeouts. After some careful evaluation we found these on the logs:
<Mon Nov 19 12:29:12 2012> End of file reached for host trk.kissmetrics.com:80
This was due to the fact that kissmetrics send metrics via get request and as such all parameters are sent on the URL. URL's have a length limit http://stackoverflow.com/questions/417142/what-is-the-maximum-length-of-a-url
Is there anyway around this?
Thank you.
The text was updated successfully, but these errors were encountered: