Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

SERVER_PORT not set in wsgi when using shared-socket #144

Closed
edevil opened this issue Jan 31, 2013 · 4 comments
Closed

SERVER_PORT not set in wsgi when using shared-socket #144

edevil opened this issue Jan 31, 2013 · 4 comments

Comments

@edevil
Copy link
Contributor

edevil commented Jan 31, 2013

I'm using shared-socket so that the master server can bind to the sockets and drop privileges. But in this mode uWSGI does not set the SERVER_PORT variable which goes against PEP 333. This poses problems for apps like Django.
@unbit
Copy link
Owner

unbit commented Jan 31, 2013

fixed in both stable and development tree

01b14f4

@unbit unbit closed this as completed Jan 31, 2013
@edevil
Copy link
Contributor Author

edevil commented Feb 9, 2013

I've noticed that you reverted this fix in the stable version. So this will only be fixed on 1.9 am I right?

@unbit
Copy link
Owner

unbit commented Feb 9, 2013

hmm i think i have made some mess... the fix is meant to be backported

@unbit
Copy link
Owner

unbit commented Feb 9, 2013

fixed

@yuzz920903 yuzz920903 mentioned this issue Mar 30, 2023
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@edevil @unbit