Skip to main content
Solved

Status code 413 Publishing Workspace to the server

  • Jul 10, 2017 7:26 PM UTC
  • 3 replies
  • 278 views
Forum|alt.badge.img

Hi,

We have a workspace file with a size of 2140kb, when we tried to upload to FME server we are getting a publish failed error:

Publish failed - FME Server encountered an error.

Request to https://myserver/fmerest/v3/repositories/dev/items returned status code 413.

HTTP Error 413 is Entity Too Large, where can I change this restriction on FME Server?

Thanks.

Best answer by geosander

If it is a standard FME Server installation (with the built-in Tomcat HTTP server and the default FME Server configuration), this should not happen. My workspaces were over 4MB and I never experienced any problems.

My guess is that your HTTP server configuration is the problem here. Which one are you using? IIS, Tomcat, Apache...?

View original
    This post is closed to further activity.
    It may be an old question, an answered question, an implemented idea, or a notification-only post.
    Please check post dates before relying on any information in a question or answer.
    For follow-up or related questions, please post a new question or idea.
    If there is a genuine update to be made, please contact us and request that the post is reopened.

    3 replies

    geosander
    Forum|alt.badge.img+7
    • geosander
    • Best Answer
    • Jul 10, 2017 8:08 PM UTC

    If it is a standard FME Server installation (with the built-in Tomcat HTTP server and the default FME Server configuration), this should not happen. My workspaces were over 4MB and I never experienced any problems.

    My guess is that your HTTP server configuration is the problem here. Which one are you using? IIS, Tomcat, Apache...?

    Forum|alt.badge.img

    If it is a standard FME Server installation (with the built-in Tomcat HTTP server and the default FME Server configuration), this should not happen. My workspaces were over 4MB and I never experienced any problems.

    My guess is that your HTTP server configuration is the problem here. Which one are you using? IIS, Tomcat, Apache...?

    Hi,

     

    I'm using nginx as a reverse proxy, I add to my config:
    # set client body size to 20M #
    client_max_body_size 20M;

    And start working.

     

    Thanks!!!
      geosander
      Forum|alt.badge.img+7
      • geosander
      • Jul 11, 2017 7:22 AM UTC
      Hi,

       

      I'm using nginx as a reverse proxy, I add to my config:
      # set client body size to 20M #
      client_max_body_size 20M;

      And start working.

       

      Thanks!!!
      Glad you figured it out and thanks for sharing the solution. It helps others who might have the same issue!

      Community Stats

      32,990
      Posts
      125,025
      Replies
      41,911
      Members
      Terms & ConditionsAccessibility statement
      A product of
      Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.