Dnia piątek, 30 grudnia 2011 14:07:38 Łukasz Mierzwa pisze:
> Hi,
>
> first of all congratulations on the release of 1.0
> 1.0 version stands for a lot of work that You put into uWSGI and it's a real
> pleasure to use it.
>
> Does fastrouter support using wildcard domains? I've added
>
> subscribe-to = 172.16.200.53:2626:*.app.domain.com
>
> to my vassal config. Fastrouter shows this domain in stats output:
>
> { "key": "*.app.domain.com",
> "hits": 0,
> "nodes": [
> {"name": "172.16.200.55:3001", "modifier1": 0,
> "modifier2": 0, "last_check": 1325249838, "requests": 0, "tx": 0, "cores":
> 4, "load": 0, "ref": 0, "failcnt": 0, "death_mark": 0}
> ]
> },
>
> But no request is being forwarded to my vassal if I try to get
> xxx.app.domain.com and I'm getting 502 from nginx.
> I have:
>
> uwsgi_param UWSGI_FASTROUTER_KEY $host;
>
> in nginx configuration. Should it work? Does fastrouter know how to handle
> wildcard domains?
P.S. It seems that '*' is treated as ordinal character as setting Host header
to *.app.domain.com works:
curl -I -H 'Host: *.app.domain.com' xxx.app.domain.com
HTTP/1.1 405 METHOD NOT ALLOWED
Server: nginx/1.0.11
Content-Type: text/html; charset=utf-8
Connection: keep-alive
Content-Length: 0
Vary: Cookie
ETag: "d41d8cd98f00b204e9800998ecf8427e"
Allow: GET
Date: Fri, 30 Dec 2011 13:08:52 GMT
Łukasz Mierzwa
_______________________________________________
uWSGI mailing list
[email protected]
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
