Janrain php-openid 查询损坏
我正在运行 janrains php5 php-openid 的检测脚本，但我一直遇到此错误。
Query Corruption
================
Your web server seems to corrupt queries. Received , expected a=%26b.
Check for mod_encoding.
我
HTTP Fetching
=============
This PHP installation has support for libcurl. Good.
An HTTP request was completed. *An unexpected URL was returned:
<https://gist.github.com/raw/465630/c57eff55ebc0c54973903af5f72bac72762cf4f4/helloworld>.*
Your PHP installation appears to support SSL, so it will be able to process
HTTPS identity URLs and server URLs.
已经在 mod 文件夹中找到了 mod_encoding 并启用了它，但我不确定如何处理它，因为我似乎无法轻松找到有关它的文档。我正在为 debian lenny 运行最新的 apache php。我回家后会有具体版本！谢谢！！
im running the detect script for janrains php5 php-openid and I keep running into this error.
Query Corruption
================
Your web server seems to corrupt queries. Received , expected a=%26b.
Check for mod_encoding.
and this
HTTP Fetching
=============
This PHP installation has support for libcurl. Good.
An HTTP request was completed. *An unexpected URL was returned:
<https://gist.github.com/raw/465630/c57eff55ebc0c54973903af5f72bac72762cf4f4/helloworld>.*
Your PHP installation appears to support SSL, so it will be able to process
HTTPS identity URLs and server URLs.
Ive located mod_encoding on the mod folder and enabled it, but im not sure what to do with it because I cant seem to find documentation on it easily. I am running the lastest apache php for debian lenny. I will have specific versions when I get home! Thanks!!
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
关于意外的 URL： detector.php 的第 437 行和 438 行（至少在我几天前下载的版本中）设置了它尝试获取的 URL 以及它期望重定向到的 URL：
所以它期望 < code>http://www.openidenabled.com/resources/php-fetch-test 将被重定向到
http://www.openidenabled.com/resources/php-fetch-test.txt。但正如您所看到的，如果您在浏览器中访问第一个 URL，则不会发生这种情况。我的猜测是，它是在某个时候以这种方式设置的，并且在后来的某个时间，行为发生了变化，但没有人更新 detector.php 脚本。事实上，www.openidenabled.com 域中的任何 URL（或者至少是我尝试过的所有少量 URL）都将重定向到
http://www.janrain.com/openid-已启用。您可以采取多种措施来解决此问题。最简单的方法是忽略它，因为事情很可能会按预期运行，并且您不会遇到任何问题。 （当我运行
detect.php时，我收到相同的消息，并且我的代码可以正常工作。）如果您想成为一个好公民，请在项目中记录错误。
如果需要，您可以设置自己的重定向测试或查找正在重定向的 URL，并更改
detect.php 中的$fetch_url和$expected_url的值适当地编写脚本。或者保留$fetch_url不变，但将$expected_url值更改为http://www.janrain.com/openid-enabled。但简而言之，您的设置可能没有任何问题。
Regarding the unexpected URL: Lines 437 and 438 of detect.php (at least in the version I downloaded a few days ago) set the URL that it tries to fetch and the URL that it expects to be redirected to:
So it's expecting that
http://www.openidenabled.com/resources/php-fetch-testwill be redirected tohttp://www.openidenabled.com/resources/php-fetch-test.txt. But as you can see if you go to the first URL in a browser, that's not what happens. My guess is that it was set up that way at some point, and at some later time the behavior changed, but no one every updated the detect.php script.In fact it appears that any URL (or at least all of the small number of URls that I've tried) in the www.openidenabled.com domain will redirect to
http://www.janrain.com/openid-enabled.There are several things you can do about this. The easiest would be to ignore it as things are most likely behaving as expected and you will not experience any problems. (I get the same message when I run
detect.phpand my code otherwise works.)If you want to be a good citizen, log a bug with the project.
If you want, you can set up your own redirect test or find URLs that are redirecting and change the value of
$fetch_urland$expected_urlin thedetect.phpscript appropriately. Or leave$fetch_urlas is but change the$expected_urlvalue tohttp://www.janrain.com/openid-enabled.But in short, it's probably the case that nothing is wrong with your setup.