Use full domain like "myproject.tunnel.example.com" as client's id instead of "myproject".
Combine sub_domain and current hostname as client's id when creating new client.
Check the clients object with full hostname when new request comes in.
Use full domain like "myproject.tunnel.example.com" as client's id instead of "myproject".
Combine sub_domain and current hostname as client's id when creating new client.
Check the clients object with full hostname when new request comes in.
This pull request added multi-level subdomain support but didn't pass the websocket tests.
I tried to fix, but I found the original master branch cannot pass neither. So I think it's better not to fix websocket support in this pull request.
@defunctzombie what do you think?
This pull request added multi-level subdomain support but didn't pass the websocket tests.
I tried to fix, but I found the original master branch cannot pass neither. So I think it's better not to fix websocket support in this pull request.
@defunctzombie what do you think?
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Use full domain like "myproject.tunnel.example.com" as client's id instead of "myproject".
Combine sub_domain and current hostname as client's id when creating new client.
Check the clients object with full hostname when new request comes in.
This pull request added multi-level subdomain support but didn't pass the websocket tests.
I tried to fix, but I found the original master branch cannot pass neither. So I think it's better not to fix websocket support in this pull request.
@defunctzombie what do you think?
Closing in favor of #65
Pull request closed