I came across this in the test code which leads me to believe it is not, but wondering if there is any update on when dash routes might support this or if there is another way around it (besides reloading the URL again).
Currently behavior is page returns "Loading..." to the browser and I see this from the server (before reloading):
$ python3 test_dash_auth.py
http://hello:wor:ld@barolo:47125
Dash is running on http://barolo:47125/
* Serving Flask app "test_dash_auth" (lazy loading)
* Environment: production
WARNING: This is a development server. Do not use it in a production deployment.
Use a production WSGI server instead.
* Debug mode: off
* Running on http://barolo:47125/ (Press CTRL+C to quit)
192.168.0.186 - - [30/Sep/2020 21:15:35] "GET / HTTP/1.1" 401 -
192.168.0.186 - - [30/Sep/2020 21:15:35] "GET / HTTP/1.1" 200 -
192.168.0.186 - - [30/Sep/2020 21:15:35] "GET /assets/bWLwgP.css?m=1601518562.6601 HTTP/1.1" 403 -
192.168.0.186 - - [30/Sep/2020 21:15:35] "GET /_dash-component-suites/dash_renderer/polyfill@7.v1_8_2m1601187996.8.7.min.js HTTP/1.1" 403 -
192.168.0.186 - - [30/Sep/2020 21:15:35] "GET /_dash-component-suites/dash_renderer/react@16.v1_8_2m1601187996.13.0.min.js HTTP/1.1" 403 -
192.168.0.186 - - [30/Sep/2020 21:15:35] "GET /_dash-component-suites/dash_renderer/react-dom@16.v1_8_2m1601187996.13.0.min.js HTTP/1.1" 403 -
192.168.0.186 - - [30/Sep/2020 21:15:35] "GET /_dash-component-suites/dash_renderer/prop-types@15.v1_8_2m1601187996.7.2.min.js HTTP/1.1" 403 -
192.168.0.186 - - [30/Sep/2020 21:15:35] "GET /_dash-component-suites/dash_html_components/dash_html_components.v1_1_1m1599668561.min.js HTTP/1.1" 403 -
192.168.0.186 - - [30/Sep/2020 21:15:35] "GET /_dash-component-suites/dash_core_components/dash_core_components.v1_12_1m1600343520.min.js HTTP/1.1" 403 -
192.168.0.186 - - [30/Sep/2020 21:15:35] "GET /_dash-component-suites/dash_core_components/dash_core_components-shared.v1_12_1m1600343520.js HTTP/1.1" 403 -
192.168.0.186 - - [30/Sep/2020 21:15:35] "GET /_dash-component-suites/dash_renderer/dash_renderer.v1_8_2m1601187996.min.js HTTP/1.1" 403 -
192.168.0.186 - - [30/Sep/2020 21:15:35] "GET /_dash-component-suites/dash_renderer/react@16.v1_8_2m1601187996.13.0.min.js HTTP/1.1" 403 -
192.168.0.186 - - [30/Sep/2020 21:15:35] "GET /_dash-component-suites/dash_renderer/react-dom@16.v1_8_2m1601187996.13.0.min.js HTTP/1.1" 403 -
192.168.0.186 - - [30/Sep/2020 21:15:35] "GET /_dash-component-suites/dash_renderer/prop-types@15.v1_8_2m1601187996.7.2.min.js HTTP/1.1" 403 -
192.168.0.186 - - [30/Sep/2020 21:15:35] "GET /_dash-component-suites/dash_html_components/dash_html_components.v1_1_1m1599668561.min.js HTTP/1.1" 403 -
192.168.0.186 - - [30/Sep/2020 21:15:35] "GET /_dash-component-suites/dash_core_components/dash_core_components.v1_12_1m1600343520.min.js HTTP/1.1" 403 -
192.168.0.186 - - [30/Sep/2020 21:15:35] "GET /_dash-component-suites/dash_core_components/dash_core_components-shared.v1_12_1m1600343520.js HTTP/1.1" 403 -
192.168.0.186 - - [30/Sep/2020 21:15:35] "GET /_dash-component-suites/dash_renderer/dash_renderer.v1_8_2m1601187996.min.js HTTP/1.1" 403 -
192.168.0.186 - - [30/Sep/2020 21:15:35] "GET /assets/favicon.ico?m=1601263521.8334005 HTTP/1.1" 403 -
I came across this in the test code which leads me to believe it is not, but wondering if there is any update on when dash routes might support this or if there is another way around it (besides reloading the URL again).
Currently behavior is page returns "Loading..." to the browser and I see this from the server (before reloading):