Jump to content
Claris Engage 2025 - March 25-26 Austin Texas ×
The Claris Museum: The Vault of FileMaker Antiquities at Claris Engage 2025! ×

This topic is 895 days old. Please don't post here. Open a new topic instead.

Recommended Posts

Posted (edited)

I noticed my server didn't have http 2 enabled and thought it was because I was on Windows Server 2016.

I have just installed a new VM with Windows Server 2019 and http 2 is still not enabled. Any ideas why this would be?

According to Claris it shouldn't require any configuration. I am using FileMaker Server 19.1.2 (as 19.2.1 wouldn't install for some reason).

Edit: Think I found the issue - it requires 19.2.1, which I couldn't install as the installer didn't work. Oh well - hopefully sort it soon.

Edited by jaboda
  • 2 months later...
Posted (edited)

Does IIS have http2 at all? The major difference between http1.x and http2 from an application perspective is that http2 has mechanisms in place to avoid tcp slow start. I know that nginx and apache both have http2 in place; however there are no major benefits to http2 unless your solution has multiples of small files required for the same use case. https://blog.stackpath.com/tcp-slow-start/

Edited by ggt667
Posted
4 hours ago, ggt667 said:

Does IIS have http2 at all? The major difference between http1.x and http2 from an application perspective is that http2 has mechanisms in place to avoid tcp slow start. I know that nginx and apache both have http2 in place; however there are no major benefits to http2 unless your solution has multiples of small files required for the same use case. https://blog.stackpath.com/tcp-slow-start/

Yes it does and it's working now I've upgraded to 19.2.1.

  • 1 year later...
  • Newbies
Posted

I have version 19.3.1.47 running but when I test I only seem to have http/1.1 running.... The Server is running Windows 2016

There seems to be some info suggesting it is enabled by filemaker rather than IIS. There isn't much in the way of support notes on this specific to filemaker other than Filemaker Support notes saying:

"In Windows, FileMaker Server installs with HTTP/2 enabled. No other configuration or consideration is required to take advantage of HTTP/2 in FileMaker Server."

 

I beg to differ.... HTTP/1.1 200 OK

Posted

Not sure why that would be as it should work.

Sometimes I've had configuration issues which required uninstalling FileMaker Server and IIS and reinstalling. Might be worth trying.

This topic is 895 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.