Ad Widget

Collapse

Request-URI Too Long

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • duncan9562
    Member
    • Jan 2017
    • 46

    #1

    Request-URI Too Long

    Hi guys,

    We have a situation where we are trying to build a graph that has some 1389 item values.

    When looking in Latest Data, we can select the relevant values that we want to build the graph with, but gives the error:-
    We are sorry, the maximum possible number of elements to remember has been reached
    If I ignore this, and proceed to go to "Display stacked graph", I then get the error:-
    Request-URI Too Long

    The requested URL's length exceeds the capacity limit for this server.
    I guess I am hitting two limits here, one in Zabbix and one in PHP / Apache but I'm not sure.

    For reference, I am using the zabbix-frontend-php package on Debian Jessie, version 1:3.4.2-1+jessie.

    Any help / guidance would be greatly appreciated.
  • jan.garaj
    Senior Member
    Zabbix Certified Specialist
    • Jan 2010
    • 506

    #2
    Try to increase the Apache limits for limit request line and limit request field size.
    Devops Monitoring Expert advice: Dockerize/automate/monitor all the things.
    My DevOps stack: Docker / Kubernetes / Mesos / ECS / Terraform / Elasticsearch / Zabbix / Grafana / Puppet / Ansible / Vagrant

    Comment

    • reekjohns
      Junior Member
      • Nov 2019
      • 4

      #3
      Under Apache, the limit is a configurable value, LimitRequestLine. Change this value to something larger than its default of 8190 if you want to support a longer request URI. Extremely long URLs are usually a
      mistake. If you keep URLs under 2000 characters , they'll work in virtually any combination of client and server software. URI actually have a character limit depending on several things. Chrome limits url length of 2MB for practical reasons and to avoid causing denial-of-service problems in inter-process communication. On most platforms, Chrome's omnibox limits URL display to 32kB (kMaxURLDisplayChars ) although a 1kB limit is used on VR platforms. IE - 2083 characters, Firefox - 2047 characters, Safari 80000 characters and Opera 190,000 characters.

      To resolve the problem :
      • By POST request: Convert query string to json object and sent to API request with POST
      • By GET request: Max length of request is depend on sever side as well as client side. Most webserver have limit 8k which is configurable. On the client side the different browser has different limit. The browser IE and Safari limit to 2k, Opera 4k and Firefox 8k. means the max length for the GET request is 8k and min request length is 2k.
      If exceed the request max length then the request truncated outside the limit by web server or browser without any warning. Some server truncated request data but the some server reject it because of data lose and they will return with response code 414.

      Comment

      Working...