Comments (9)
can you try with HEAD, or can you remove the spawn of the non-https server on port 80 ? i suspect hook are not correctly set
from uwsgi.
Hiya, thanks for the response, and for the great work you guys have done on uwsgi!
I've removed the http directive and get the same thing. I also get no response from s_client when I try and issue any HTTP commands. Here's the output from a HEAD followed by .
https://gist.github.com/3937635
Here's the output from the console if I hit it with a browser. It's sending HTTP/1.1. I don't know if that's an issue:
[pid: 18404|app: 0|req: 3/3] 192.168.56.1 () {36 vars in 586 bytes} [Mon Oct 22 18:12:30 2012] GET / => generated 5958 bytes in 80 msecs (HTTP/1.1 200) 2 headers in 73 bytes (1 switches on core 0)
and fetching a single static file instead of /
[pid: 31331|app: 0|req: -1/1] 192.168.56.1 () {36 vars in 626 bytes} [Mon Oct 22 18:21:36 2012] GET /static/css/style.css => generated 0 bytes in 6 msecs via sendfile() (HTTP/1.1 200) 2 headers in 88 bytes (0 switches on core 0)
which generates (Error code: ssl_error_rx_record_too_long) and shows the request being served successfully as cleartext, with tcpdump.
and the config:
;uWSGI instance configuration
[uwsgi]
ini = /etc/uwsgi.ini
master = true
socket = /var/run/uwsgi.sock
https = 0.0.0.0:443,/root/server.crt,/root/server.key
http-to = /var/run/uwsgi.sock
python-path = /usr/local/ph
check-static = /usr/local/ph/www
wsgi-file = /usr/local/ph/www/wsgi_app.py
show-config = true
;end of configuration
This is all running on openbsd5.1. Standalone works great if I don't use HTTPS. Let me know if there's anything else I can do to help. I'm working on the UI for a network appliance and I'd love to be able to use uwsgi standalone instead of through a webserver.
Cheers!
Colin.
from uwsgi.
it looks like a openbsd-specific issue (maybe openssl-related) i will address it as soon as possibile.
Thanks for the report
from uwsgi.
Just tried current HEAD on OpenBSD 5.1 and it works normally, can you try that ?
from uwsgi.
I've tried several of the latest snapshots and it behaves differently since the 1.4 tag. It looks like it's encrypting, but it doesn't send me any data. Empty response. Here's the console output with the config: https://gist.github.com/3940523
HTTP doesn't work either in this build. Same problem, empty response. Can you show me what you're doing to test it? If I can start with that, hopefully I can find the problem.
from uwsgi.
Breakthrough! I've got 1.3-stable working with the following config: https://gist.github.com/3940995 1.4 still doesn't work, but that's ok :) I'm running without any socket communication. Just direct http.
from uwsgi.
just found a bug in kqueue, now HEAD should work. --https-to-http does not work in HEAD, i will port it tomorrow. Let me know if other things works on OpenBSD. Thanks a lot
from uwsgi.
Will do. Thanks for the help. BTW, I've forked uwsgi and included a plugin I wrote to implement hosts_access as a router. Please have a look!
https://github.com/brainbitsca/uwsgi/tree/master/plugins/router_access
from uwsgi.
great, i will put comments on 'gray' areas, then feel free to make a pull request
from uwsgi.
Related Issues (20)
- How do I silence the startup messages outputed by UWSGI? HOT 1
- Troubleshooting uWSGI Log Rotation Configuration in a Django Container Environment
- Attaching debugger to process
- Undefined Behavior: `strncpy` from `NULL` HOT 3
- uwsgi compilation failed with openssl-1.1 python3.10 HOT 3
- Sigmask cause some commands segmentfault
- -Wformat-signedness causes compilation error with CLANG 16.0.6 HOT 2
- Workers segfaulting (threading related?) HOT 3
- Harakiri process is starting earlier than expected HOT 7
- Workers terminated by SigKill 9
- flag -Wformat-signedness HOT 4
- Getting 404 while using uwsgi with NginX in Django deployment HOT 1
- uwsgi worker dying at high request load with error "taking too much time to die...NO MERCY !!!" HOT 3
- Does uwsgi want to support WSGI+ ?
- Is the graceful harakiri signal sent to the process or thread? HOT 2
- Trouble building 2.0.24 python plugin HOT 1
- Segmentation Fault with Python3.12
- Not compatible with python 3.12 HOT 1
- BlockingIOError: [Errno 11] write could not complete without blocking
- OSError: [Errno 90] Message too long
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from uwsgi.