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
I'm using airflow standalone to start a local airflow instance for development and debugging purposes. This works without any error occurring when starting up airflow. However, when I open airflow in the browser, not any of the assests (css and javascript) can be loaded in chrome, as it fails with 'net::ERR_INVALID_HTTP_RESPONSE' in Chromium browsers. I've then tried to use Firefox to make sure that this is not a pure Chrome issue. In Firefox I at least get the content loaded, but noticed that there are HTTP Headers appended to all these responses like so:
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi there,
I'm using
airflow standalone
to start a local airflow instance for development and debugging purposes. This works without any error occurring when starting up airflow. However, when I open airflow in the browser, not any of the assests (css and javascript) can be loaded in chrome, as it fails with 'net::ERR_INVALID_HTTP_RESPONSE' in Chromium browsers. I've then tried to use Firefox to make sure that this is not a pure Chrome issue. In Firefox I at least get the content loaded, but noticed that there are HTTP Headers appended to all these responses like so:Running on:
Is there any configuration option to stop this being added?
Beta Was this translation helpful? Give feedback.
All reactions