Forums
(@userdeck)
7 years, 9 months ago
We’re sorry you ran into that issue. We’re not exactly sure how this happened, but it has been fixed. We believe our upstream ISP made a change on our proxy that was adding this header, but we did manage to get it fixed.