From 36b90436e29e9bf0ab307467ffa71bcb700758e5 Mon Sep 17 00:00:00 2001 From: Yannick Jadoul Date: Fri, 14 Jun 2024 12:15:23 +0200 Subject: [PATCH] Fix broken Flask-CORS link in docs --- docs/examples/web_service.ipynb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/examples/web_service.ipynb b/docs/examples/web_service.ipynb index 7ced0acd..99add7d1 100644 --- a/docs/examples/web_service.ipynb +++ b/docs/examples/web_service.ipynb @@ -225,7 +225,7 @@ "cell_type": "markdown", "metadata": {}, "source": [ - "Again, one thing to take into account is the security of running such a web server. However, apart from deploying the flask server in a secure and performant way, we also need one extra thing to circumvent a standard security feature of the browser. Without handling Cross Origin Resource Sharing (CORS) on the server, the JavaScript code on the client side will not be able to access the web service's reply. A Flask extension exists however, [Flask-CORS](https://flask-cors.readthedocs.io/), and we refer to its documentation for further details." + "Again, one thing to take into account is the security of running such a web server. However, apart from deploying the flask server in a secure and performant way, we also need one extra thing to circumvent a standard security feature of the browser. Without handling Cross Origin Resource Sharing (CORS) on the server, the JavaScript code on the client side will not be able to access the web service's reply. A Flask extension exists however, [Flask-CORS](https://flask-cors.corydolphin.com/), and we refer to its documentation for further details." ] }, {