mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-26 01:45:54 +03:00
[PR #376] [MERGED] expand the maximum size of the forward_host #3235
Labels
No labels
awaiting feedback
bug
cannot reproduce
dns provider request
duplicate
enhancement
enhancement
enhancement
good first issue
help wanted
invalid
need more info
no certbot plugin available
product-support
pull-request
question
stale
troll
upstream issue
v2
v2
v2
v3
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nginx-proxy-manager-NginxProxyManager#3235
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/NginxProxyManager/nginx-proxy-manager/pull/376
Author: @spalger
Created: 4/16/2020
Status: ✅ Merged
Merged: 4/16/2020
Merged by: @jc21
Base:
develop← Head:expand-forward-host-size📝 Commits (4)
4c60bfbMerge pull request #370 from jc21/develop995db12remove arbitrary length limit of forward_host1d23d5cremove maxlength from html too3af560cswitch to 255 limit to match db📊 Changes
2 files changed (+2 additions, -2 deletions)
View changed files
📝
backend/schema/endpoints/proxy-hosts.json(+1 -1)📝
frontend/js/app/nginx/proxy/form.ejs(+1 -1)📄 Description
I'm trying to setup a proxy host to a hostname that is 56 characters long and that's not allowed by the schema for the proxy host for some reason :/ I think it's probably best to avoid arbitrary limits like this so I've removed it from the schema, but I could also set it to 255 or something if you prefer.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.