Skip to main content
Solved

Status code 413 Publishing Workspace to the server


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
Did this help you find an answer to your question?

3 replies

geosander
Forum|alt.badge.img+7
  • Best Answer
  • July 10, 2017

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
geosander wrote:

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
  • July 11, 2017
velasquezvictor wrote:
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!

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings