correct routing of urls

34 views
Skip to first unread message

Ram

unread,
Aug 1, 2012, 4:33:12 PM8/1/12
to pagekite...@googlegroups.com

Hi Bjarni,

I am running a pagekite server on an ubuntu box and routing urls thru it. I just updated to 0.5.0 and am noticing this problem (am not sure this was there before). I only use 20_frontends.rc with port 443. When I goto https://randomname.mydomain.com -- sometimes i see it being forwarded to one of the currently online domains (even when the 20_frontends.rc does not have randomname in it)! How can I debug this?

Thanks,
--Ram

Ram

unread,
Aug 1, 2012, 4:38:40 PM8/1/12
to pagekite...@googlegroups.com

How can I stop this from happening would be my correct question:

ts=50198e67; t=2012-08-01T15:15:35; ll=11d7; debug=No back-end; on_port=443; proto=https; domain=randomname.mydomain.com; is=FE; id=s55c/~51.138:57679
ts=50198e67; t=2012-08-01T15:15:35; ll=11d8; eof=1; id=s55c/~51.138:57679
ts=50198e67; t=2012-08-01T15:15:35; ll=11d9; accept=~51.138:57680; id=s0
ts=50198e67; t=2012-08-01T15:15:35; ll=11da; debug=No SNI - trying: onlinename.mydomain.com; id=s55d/~51.138:57680
ts=50198e67; t=2012-08-01T15:15:35; ll=11db; domain=onlinename.mydomain.com; on_port=443; proto=https; is=FE; id=s55d/~51

Bjarni Rúnar Einarsson

unread,
Aug 1, 2012, 5:29:36 PM8/1/12
to pagekite...@googlegroups.com

Sorry of this is short, I am on the road. :-)

The key there is the "no SNI" message. You need to be sure all clients are modern and support the TLS SNI extension for correct routing of end-to-end HTTPS.

- Bjarni

Reply all
Reply to author
Forward
0 new messages