# Artifacts.elastic.co forced HTTPS redirect **URL:** \ **Category:** Elasticsearch\ **Created:** [March 17, 2021, 11:37am UTC](https://discuss.elastic.co/t/artifacts-elastic-co-forced-https-redirect/267491 "2021-03-17T11:37:54Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![sfinke0](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sfinke0/32/85678_2.png) [@sfinke0](https://discuss.elastic.co/u/sfinke0)\ **Post date:** [March 17, 2021, 11:37am UTC](https://discuss.elastic.co/t/artifacts-elastic-co-forced-https-redirect/267491/1 "2021-03-17T11:37:54Z")
Hi there, we recently noticed a forced HTTPS redirect on the [artifacts.elastic.co](http://artifacts.elastic.co) endpoints. Since we use apt-caching (apt-cacher-ng) for more than 1000 hosts this breaks its functionality for plain HTTP proxying and caching. Would it be possible to enable the plain HTTP endpoint without HTTP Status 308 redirect again? Thanks in advance Sebastian ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [March 22, 2021, 9:26pm UTC](https://discuss.elastic.co/t/artifacts-elastic-co-forced-https-redirect/267491/2 "2021-03-22T21:26:45Z")
Do [any of the documented upstream options for HTTPS support](https://www.unix-ag.uni-kl.de/~bloch/acng/html/howtos.html#ssluse) would work for you? ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [April 19, 2021, 9:27pm UTC](https://discuss.elastic.co/t/artifacts-elastic-co-forced-https-redirect/267491/3 "2021-04-19T21:27:24Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.