Skip to content

Commit

Permalink
Reflect websocket proxy support on README (facebook#1013) (facebook#1483
Browse files Browse the repository at this point in the history
)

* Reflect websocket proxy support on README

* Add 'the'
  • Loading branch information
frontsideair authored and gaearon committed Feb 4, 2017
1 parent fd99f8f commit 8105a86
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion template/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -650,7 +650,7 @@ Fetch API cannot load http://localhost:4000/api/todos. No 'Access-Control-Allow-

Keep in mind that `proxy` only has effect in development (with `npm start`), and it is up to you to ensure that URLs like `/api/todos` point to the right thing in production. You don’t have to use the `/api` prefix. Any unrecognized request without a `text/html` accept header will be redirected to the specified `proxy`.

Currently the `proxy` option only handles HTTP requests, and it won’t proxy WebSocket connections.<br>
The `proxy` option supports HTTP, HTTPS and WebSocket connections.<br>
If the `proxy` option is **not** flexible enough for you, alternatively you can:

* Enable CORS on your server ([here’s how to do it for Express](http://enable-cors.org/server_expressjs.html)).
Expand Down

0 comments on commit 8105a86

Please sign in to comment.