[GH-ISSUE #2660] Add ngx_http_sub_module #1834

New issue

Closed

opened 2026-02-26 07:32:40 +03:00 by kerem · 2 comments

kerem commented

2026-02-26 07:32:40 +03:00

Owner

Originally created by @Ministorm3 on GitHub (Mar 7, 2023).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2660

Is your feature request related to a problem? Please describe.
I have configured Nginx proxy manager to provide auth for a server application that has no built in system for handling auth. Due to severe limitations at the client end of the application, I have configured the server to accept some raw query string parameters to handle the auth. For example, https://application/directory?auth=knz45c7984rcl4wm8y (I know this is not a very secure setup. It is the best I can do for now while the application still has these limitations)

Because this is the only way that auth can be handled for this particular application, we need all of the URLs that the application responds with to have this auth parameter as well. Unfortunately, since the server application is not smart enough to realize this is all happening, it does not return URLs with the correct auth key.

Describe the solution you'd like
I would like to utilize ngx_http_sub_module to modify the HTTP responses to include the auth key in the GET parameters. It looks like this would need to be added to the nginx build in order to utilize its functionality.

Describe alternatives you've considered
I explored implementing auth into the application itself. But I am not the original developer of the application and couldn't begin to figure out how to implement it. Additionally, I would like to protect the app at the NGINX level. The original application has no auth built in, and therefore, I cannot trust that any endpoint it provides is secure without NGINX putting some auth in front of it.

That being said, I am open to any alternatives that someone can suggest.

Originally created by @Ministorm3 on GitHub (Mar 7, 2023). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2660 **Is your feature request related to a problem? Please describe.** I have configured Nginx proxy manager to provide auth for a server application that has no built in system for handling auth. Due to severe limitations at the client end of the application, I have configured the server to accept some raw query string parameters to handle the auth. For example, https://application/directory?auth=knz45c7984rcl4wm8y (I know this is not a very secure setup. It is the best I can do for now while the application still has these limitations) Because this is the only way that auth can be handled for this particular application, we need all of the URLs that the application responds with to have this auth parameter as well. Unfortunately, since the server application is not smart enough to realize this is all happening, it does not return URLs with the correct auth key. **Describe the solution you'd like** I would like to utilize ngx_http_sub_module to modify the HTTP responses to include the auth key in the GET parameters. It looks like this would need to be added to the nginx build in order to utilize its functionality. **Describe alternatives you've considered** I explored implementing auth into the application itself. But I am not the original developer of the application and couldn't begin to figure out how to implement it. Additionally, I would like to protect the app at the NGINX level. The original application has no auth built in, and therefore, I cannot trust that any endpoint it provides is secure without NGINX putting some auth in front of it. That being said, I am open to any alternatives that someone can suggest.

kerem

2026-02-26 07:32:40 +03:00

closed this issue
added the
enhancement

stale
labels

kerem commented

2026-02-26 07:32:40 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Jan 26, 2024):

Issue is now considered stale. If you want to keep it open, please comment 👍

@github-actions[bot] commented on GitHub (Jan 26, 2024): Issue is now considered stale. If you want to keep it open, please comment :+1:

kerem commented

2026-02-26 07:32:40 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Mar 12, 2025):

Issue was closed due to inactivity.

@github-actions[bot] commented on GitHub (Mar 12, 2025): Issue was closed due to inactivity.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/nginx-proxy-manager-NginxProxyManager#1834

No description provided.

Rows
Columns