Skip to content
This repository was archived by the owner on Jan 7, 2018. It is now read-only.

Conversation

@GUI
Copy link
Member

@GUI GUI commented Sep 22, 2015

It was possible that nginx would bomb if an API backend was added with a long hostname. The exact length that would trigger this error varied, since nginx's default lengths actually varied depending on the CPU type. But this should fix things so that we should properly support hostnames up to 110 characters long regardless of CPU defaults.

Fixes NREL/api-umbrella#168

It was possible that nginx would bomb if an API backend was added with a
long hostname. The exact length that would trigger this error varied,
since nginx's default lengths actually varied depending on the CPU type.
But this should fix things so that we should properly support hostnames
up to 110 characters long regardless of CPU defaults.

Fixes NREL/api-umbrella#168
GUI added a commit that referenced this pull request Sep 22, 2015
Fix handling of long hostnames
@GUI GUI merged commit 22cbec7 into master Sep 22, 2015
@GUI GUI deleted the long-hostnames branch September 22, 2015 19:50
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Adding a new backend API and accessing it returns 404 via nginx

2 participants