You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
An alternative could be to aggregate existing transporters in the lineup, similar to the radar plugin, and offer a choice of them instead. Maybe an existing, trailing /proxy within their URIs can be a condition, loose and strict enough, syntactically and semantically speaking, in the same time.
The text was updated successfully, but these errors were encountered:
Ah, so that localhost:4020 that I saw yesterday was of my own doing. The future/proxy feature seems to have been left incomplete. You make good suggestions. Is there an ideal test case to code against? Maybe two cases? Wikipedia would be one but it is not that simple.
The Future plugin relies on a locally listening
transport-proxy
to provide the/proxy
endpoint for ghost pages generation via said transporter.wiki-client/lib/future.coffee
Line 16 in 3c9110a
An alternative could be to aggregate existing transporters in the lineup, similar to the radar plugin, and offer a choice of them instead. Maybe an existing, trailing
/proxy
within their URIs can be a condition, loose and strict enough, syntactically and semantically speaking, in the same time.The text was updated successfully, but these errors were encountered: