DotNetOpenAuth 将弹出窗口设置为发布而不是获取

发布于 2024-12-06 19:23:07 字数 473 浏览 0 评论 0原文

我能够在我的 MVC3 项目中设置 DotNetOpenAuth。 (花了很长时间,但终于能够获取所有缺失的部分。)

但是,现在我收到来自 Google 的 414 错误,说明请求 URL 太长。我发现谷歌说在这些情况下请求应该是一个帖子,问题就会消失。我想知道在预加载弹出窗口时是否有一种方法可以构造 post 而不是 get ?

我使用 nerddinner 作为我的垫脚石,并使用 AuthController 代码中的代码来预加载 url。 http://nerddinner.codeplex.com/SourceControl/changeset/view/70027#952619

可以在这些弹出窗口中发帖吗?或者人们是如何绕过 Google 的 414 错误的?

I was able to get the DotNetOpenAuth set up in my MVC3 project. (Took a long time, but finally was able to get all the missing pieces.)

However, now I'm getting a 414 error from Google that the request URL is too long. I found that google is saying in those cases the request should be a post and the issue would be gone. I was wondering if there was a way to construct post instead of a get when the popup windows are being pre-loaded?

I'm using nerddinner as my stepping stone, and have used the code in the AuthController code to get the url's preloaded. http://nerddinner.codeplex.com/SourceControl/changeset/view/70027#952619

Is it possible to do a post in those popups? Or how did people get around the 414 error for Google?

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

一世旳自豪 2024-12-13 19:23:07

DotNetOpenAuth 已经将长 URL 从 GET“升级”为 POST,并且在 2048 个字符长度阈值上执行此操作。偶尔有报告称此阈值太高,可以通过 web.config 文件设置进行调整。但是,我认为这不会调整客户端上的 AJAX .js 文件(还)。

如果您愿意,请 提交一个票证来描述这个问题,我们可以获得 DotNetOpenAuth 的维护版本来解决这个问题。

仅供参考,.js 文件可在 DotNetOpenAuth 项目源代码中找到,名为 OpenIdRelyingPartyControlBase.js。但由于它作为资源编译到 dotnetopenauth.dll 中并直接从那里下载到 Web 浏览器,因此使用调整后的阈值进行修复会很不方便。

DotNetOpenAuth already 'upgrades' long URLs from GET to POST, and does so at the 2048 character length threshold. There have occasionally been reports that this threshold is too high, and it is adjustable by web.config file setting. However, I don't think that adjusts the AJAX .js file on the client (yet).

If you will please file a ticket describing this problem, we can get a maintenance release of DotNetOpenAuth out that resolves this issue.

FYI the .js file is found in the DotNetOpenAuth project source code and is called OpenIdRelyingPartyControlBase.js. But since it compiles as a resource into the dotnetopenauth.dll and downloads to the web browser directly from there, it makes it inconvenient for you to fix with an adjusted threshold.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文