mik-laj edited a comment on pull request #10256: URL: https://github.com/apache/airflow/pull/10256#issuecomment-671114988
> In my backend, I simply have: https://domain.com:443 (the 443 doesn't matter here). This does not look like a valid connection configuration URI although it does appear as a valid URL, but not a valid connection configuration. ```console $ AIRFLOW_CONN_A='https://domain.com:443' airflow connections get A Conn ID: A Conn Type: https Extra: {} Host: domain.com Is Encrypted: null Is Extra Encrypted: null Port: 443 URI: https://domain.com:443 ``` In your case, this connection can be expressed using a URI: a) ``http://https%3A%2F%2Fdomain.com:443`` ```console $ AIRFLOW_CONN_A='http://domain.com:443/https' airflow connections get A Conn Id: A Conn Type: http Extra: {} Host: domain.com Id: null Is Encrypted: null Is Extra Encrypted: null Login: null Password: null Port: 443 Schema: https URI: http://domain.com:443/https ```` or b) ``http://https%3A%2F%2Fdomain.com:443`` ``` $ AIRFLOW_CONN_A='http://https%3A%2F%2Fdomain.com:443' airflow connections get A Schema: , Login: None, Password: None, extra: None Conn Id: A Conn Type: http Extra: {} Host: https://domain.com Id: null Is Encrypted: null Is Extra Encrypted: null Login: null Password: null Port: 443 Schema: '' URI: http://https%3A%2F%2Fdomain.com:443 ``` I agree that this is not what users can expect, but we have a limited ability to change it in a backward-compatible manner. > And yes, that prior issue seems related, but it was closed (seems to have been resolved), and yet it did not work for me... This ticket has been closed because it was migrated to Github, but the comments made there are valuable and there is also a description of how to save the HTTP connection configuration as a URI. https://github.com/apache/airflow/issues/7881 ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
