# 浏览器 Cookie 损坏（？）在 Azure 上迁移站点后发生

**URL:** <https://meta.discourse.org/t/browser-cookie-corruption-after-site-migration-on-azure/141574>\
**Category:** Support\
**Created:** [2020年二月14日 04:23 UTC](https://meta.discourse.org/t/browser-cookie-corruption-after-site-migration-on-azure/141574 "2020-02-14T04:23:07Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco)\
**Post date:** [2020年二月14日 05:56 UTC](https://meta.discourse.org/t/browser-cookie-corruption-after-site-migration-on-azure/141574/2 "2020-02-14T05:56:49Z")

</div>

> [@Simon\_Miller](#):
>
> inet 类型的无效输入语法:“106.70.36.109:6082”

这是一个众所周知的 Azure 错误，此处介绍了一些变通方法：

> [@Invalid input for update\_ip\_address](https://meta.discourse.org/t/invalid-input-for-update-ip-address/77085/13?u=falco):
>
> Hi, Just to add to the conversation - this is standard practice in Azure Application Gateways, and it’s infuriating. They add the port to the forwarded-for header even though they also send it in the forwarded port header. Two feedback/change requests on Microsoft which you can vote for; [Azure Application Gateway x-forwarded-for remove port information – Customer Feedback for Microsoft Azure](https://feedback.azure.com/forums/217313-networking/suggestions/33043528-azure-application-gateway-x-forwarded-for-remove-p)[Support for dropping port out of x-forwarded-for header – Customer Feedback for Microsoft Azure](https://feedback.azure.com/forums/217313-networking/suggestions/20220997-support-for-dropping-port-out-of-x-forwarded-for-h) Our …

---

_[View the full topic](https://meta.discourse.org/t/browser-cookie-corruption-after-site-migration-on-azure/141574)._