自定义 HTTP 标头在 Rails 3 和 Android 移动应用程序中通过 HTTPS 消失
快速背景。我有 Rails 3 Web 服务、Rails 3 Web 客户端和 Android 移动应用程序。客户端将 http 标头中的身份验证令牌发送到 Web 服务。
在启用 HTTPS 之前，一切正常。 HTTPS 已打开，并且停止工作。我的自定义标头不再有效。当我第一次遇到这个问题时，我正在使用 Android 应用程序，并假设它是 Android 特定的东西。我最终放弃了，只能通过在 POST/GET 参数中发送身份验证令牌来破解它。现在我回到了 Rails Web 客户端，但我遇到了同样的问题。标题根本无法通过。
对于 Rails Web 客户端，它甚至位于同一服务器上。
我完全找不到这方面的信息。有人可以帮忙吗？
Quick background. I have a Rails 3 Web Service, Rails 3 web client, and Android mobile app. The clients send an authentication token in an http header to the web service.
Before HTTPS was turned on, everything worked fine. HTTPS gets turned on, and it stops working. My custom header doesn't make it any more. When I first encountered this I was working with the Android app, and assumed it was an Android specific thing. I finally gave up and just had to hack it by sending the auth token in POST/GET params. Now that I'm back to the rails web client however, I have the same issue. The header just doesn't make it across.
In the case of the rails web client, it is even on the same server.
I can find absolutely no information on this. Can anyone help?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
不确定这是否相关，但通过 SSL 连接，库通常需要可信源和有效证书。日志有关于证书的信息吗？
Not sure if that's related, but over SSL connection the library usually requires trusted source and valid certificate. Does the logs say anything about certificate?
老问题，但让我把这个放在这里。
我在 HTTPS 中也注意到了这个问题，但是
HTTP_AUTHORIZATION标头确实解决了这个问题。因此您可以使用它来代替自定义标头。我也想知道为什么会出现这种情况。
Old question, but let me put this here.
I noticed this problem as well in HTTPS, but
HTTP_AUTHORIZATIONheaders do make it. So you can use that instead of custom headers.I would also like to know why this happens.