Opened 3 years ago

Closed 3 years ago

Last modified 3 years ago

#13335 closed enhancement (fixed)

Guide on how to use various public services for meek

Reported by: infinity0 Owned by: dcf
Priority: Medium Milestone:
Component: Obfuscation/meek Version:
Severity: Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


<dcf1> You only need a reflector-like thing when the CDN-like thing doesn't let you point to arbitrary domains.
<dcf1> Amazon CloudFront lets you point to any domain, so the reflector is the CDN itself.
<dcf1> Google only lets you point to a Google domain, so to get around that you run an app on App Engine.
<dcf1> Azure also only allows you to point to an Azure domain, so you use the PHP or WSGI code.

It would be nice to collect this information into a document in meek.git for others.

Child Tickets

Change History (5)

comment:1 Changed 3 years ago by infinity0

Owner: changed from asn to dcf
Status: newassigned

comment:2 Changed 3 years ago by dcf

What about doc/meek#Webservices? Documenting public services is the point of that wiki section. It's already used as documentation by other meek-using projects.

comment:3 Changed 3 years ago by infinity0

Ah, that's good. Could you add these links, and anything else that might be relevant, to the documentation in git?

I think it would also be good to have two documents, or two sections in the current README - one for clients (how to set up meek-client/extensions) and one for servers (how to setup meek-server/reflectors). (I can send in a patch for that, though.)

Last edited 3 years ago by infinity0 (previous) (diff)

comment:4 Changed 3 years ago by dcf

Resolution: fixed
Status: assignedclosed

I added a paragraph in 59f41975 that links to doc/meek#Webservices and tries to explain the reflector situation.

comment:5 Changed 3 years ago by dcf

Component: Pluggable transportmeek
Keywords: meek removed
Note: See TracTickets for help on using tickets.