Hi,
I have not tried it, but I believe if you set a cookie
on .domain.com to say that they are logged in (Note the leading .) ,
then you can read that cookie in all sub-domains, and check they are
logged in to domain.com.
You might have to use domain.com, instead of docs.domain.com for the
o
Hi there,
Thanks for getting back.
On 17/3/21 8:22 pm, Francis Daly wrote:
Alternatively: if you were to reverse-proxy the MediaWiki instance at
docs.domain.com/embed/, then you could potentially set a cookie on
docs.domain.com, and require that a suitable cookie is present for any
requests to
True, true, but, but... IT RUNS OVER QUIC! :D
/dns/textprotocol.org/udp/1968/quic
> On Mar 17, 2021, at 12:35, Maxim Konovalov wrote:
>
> Enterprise level disruptive innovation!
>
> Unfortunately it doesn't come from Google, won't fly.
>
> (just kidding!)
>
> On 17.03.2021 12:49, Petite Abei
Enterprise level disruptive innovation!
Unfortunately it doesn't come from Google, won't fly.
(just kidding!)
On 17.03.2021 12:49, Petite Abeille wrote:
> Slightly off-topic, but perhaps of interest — some sort of postmodernist
> plain text protocol server.
>
> Squarely on the other end of the
Slightly off-topic, but perhaps of interest — some sort of postmodernist plain
text protocol server.
Squarely on the other end of the complexity spectrum.
> Begin forwarded message:
>
> From: 🆃🆇🆃
> Subject: [ann] publictext
> Date: March 15, 2021 at 14:08:47 GMT+1
> To: Lua mailing list
> Re
On Mon, Mar 15, 2021 at 04:24:27PM +1100, Jore wrote:
Hi there,
> "a HTTP request to the
> embed.domain.com site must only get a response if the request was made by a
> user clicking a link on the docs.domain.com site"... Am I correct in
> understanding that you mean it's not reliable as headers
