fallback of domains in frontend.rc

[Ram]

In 20_frontends.rc, lets say I have 4 domain entries (Say
A.mydomain.com, B.mydomain.com ... D.mydomain.com). If anyone goes to
https://B.mydomain.com and this particular connection is down (kite
down), I would like to reroute all traffic to https://A.mydomain.com.
Same with C and D. How can this be done? (I am assuming A is on all
the time or most of the time)

Thanks,
--Ram

[Bjarni Rúnar Einarsson]

There is some experimental support for fallback routes, invoked by
using protocols named 'http2' or 'http3' instead of just 'http', but
it's not very well tested at the moment. Give it a try and let us
know if it works for you!

--
Bjarni R. Einarsson
Founder, lead developer of PageKite.

Make localhost servers visible to the world: https://pagekite.net/

[Ram]

Can you please let me know how to use http2/3? Does it work with
https?

For example if I want to route these

domain=https:myid1.mydomain.com:mypassword1
domain=https:myid2.mydomain.com:mypassword2

to say

https:offids.mydomainoff.com:<what password> ?

Thanks,

On Jan 15, 7:35 am, Bjarni Rúnar Einarsson <b...@pagekite.net> wrote:

> On Sat, Jan 14, 2012 at 5:15 PM, Ram <mobilebacku...@gmail.com> wrote:
>
> > In 20_frontends.rc, lets say I have 4 domain entries (Say
> > A.mydomain.com, B.mydomain.com ... D.mydomain.com). If anyone goes to

> >https://B.mydomain.comand this particular connection is down (kite
> > down), I would like to reroute all traffic tohttps://A.mydomain.com.

[Bjarni Rúnar Einarsson]

Hmm, I am not sure fallbacks are the right way to do this. Are you
trying to implement a friendly error page like the pagekite.net
service offers when people try to access a kite that is down?

[Ram]

Indeed I am. Thanks.

On Jan 16, 6:57 am, Bjarni Rúnar Einarsson <b...@pagekite.net> wrote:
> Hmm, I am not sure fallbacks are the right way to do this.  Are you
> trying to implement a friendly error page like the pagekite.net
> service offers when people try to access a kite that is down?
>
>
>
>
>
>
>
>
>
> On Mon, Jan 16, 2012 at 4:27 AM, Ram <mobilebacku...@gmail.com> wrote:
>
> > Can you please let me know how to use http2/3? Does it work with
> > https?
>
> > For example if I want to route these
>
> > domain=https:myid1.mydomain.com:mypassword1
> > domain=https:myid2.mydomain.com:mypassword2
>
> > to say
>
> > https:offids.mydomainoff.com:<what password> ?
>
> > Thanks,
>
> > On Jan 15, 7:35 am, Bjarni Rúnar Einarsson <b...@pagekite.net> wrote:
> >> On Sat, Jan 14, 2012 at 5:15 PM, Ram <mobilebacku...@gmail.com> wrote:
>
> >> > In 20_frontends.rc, lets say I have 4 domain entries (Say
> >> > A.mydomain.com, B.mydomain.com ... D.mydomain.com). If anyone goes to

> >> >https://B.mydomain.comandthis particular connection is down (kite

[Bjarni Rúnar Einarsson]

On Mon, Jan 16, 2012 at 5:00 PM, Ram <mobileb...@gmail.com> wrote:
>
> Indeed I am. Thanks.

Ah, ok. I think what you are looking for then is the --errorurl=
parameter. It allows you to specify the URL for a web page to serve
when the requested back-end is unavailable. If you end the URL with a
? character (question mark) then PageKite will append some arguments
explaining why the connection failed which the website can use to
customize the displayed error.

Note that this is NOT a redirect, as we did not want to break the
address in the URL bar of the user's browser. Instead, the URL is
displayed inside a frame, and the frame is returned with an HTTP code
of 500 to ensure that automated scripts, search engines and such do
not get the wrong idea and think the page has disappeared for good.

Out of curiosity, can you tell us what you are working on building?
We are always quite curious to know how PageKite is being used. :-)

[Ram]

Thanks for the help. We are a small group of people working on a
project that we have not yet made public (But hopefully soon, I'll be
able to tell). My boss told me to look into using pagekite for our
code, and hence I'm looking into it. I hear we will be getting a copy
of pagekite for use in our project soon.

Another problem I ran into today is this:

!!! REJECTED: https:mywebsite.mydomain.com (duplicate) <-- on the
backend

Debugging steps I tried:
I checked the pagekite backend command, and it looks right. I matched
the passwords, and that looks right. Then I rebooted my server, even
that did not solve the problem.
I thought this message meant that I might be running another backend
somewhere. But if I did, I should be able to access https://mywebsite.mydomain.com
-- but that website is down. Hence I concluded that probably there is
no other instance running anywhere. This used to work before. any
ideas why this might be occuring?

Thanks,
--Ram


On Jan 18, 7:38 am, Bjarni Rúnar Einarsson <b...@pagekite.net> wrote:

[Bjarni Rúnar Einarsson]

On Sat, Jan 21, 2012 at 6:03 PM, Ram <mobileb...@gmail.com> wrote:
>
> Another problem I ran into today is this:
>
> !!! REJECTED: https:mywebsite.mydomain.com (duplicate) <-- on the
> backend

I think we actually had a conversation about this on IRC - did you
sort this out?

Usually this means you have more than one pagekite running with the
same account/kite details.

[Ram]

Indeed we sorted this out, thanks.

On Jan 29, 11:43 am, Bjarni Rúnar Einarsson <b...@pagekite.net> wrote: