blocks|key|442726|text|第一种方法似乎更像是"RESTful“。您尝试获取特定资源(通过用户名或电子邮件)，如果存在，则获取该资源，或者获取状态消息"unavailable+resource“。这将是：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|442727|442728|GET+/users/username/johnwayne+(“获取”johnwayne资源/用户名availability...)|unordered-list-item|442729|442730|这应该会生成：|442731|442732|200:+if+resource+exists|442733|404:+if+|442734|+resource+not+exist|442735|第二个看起来更像是“SOAP”用户搜索web服务，你可以定义一个带有一些“参数”(用户名，电子邮件)的“函数”(/-like/-like/)……|442736|entityMap^0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|U|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|V|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|W|8|@]|9|@]|A|$]]|$1|G|3|H|5|6|7|X|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|J|3|K|5|E|7|Z|8|@]|9|@]|A|$]]|$1|L|3|M|5|E|7|10|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|11|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|12|8|@]|9|@]|A|$]]|$1|R|3|-4|5|6|7|13|8|@]|9|@]|A|$]]]|S|$]]

The first approach does seem to be more "RESTful". You try to GET a specific resource (by username or email) and get it if it exists or get a status message "unavailable resource". This would be:

<ul>
<li>GET /users/username/johnwayne (to "get" johnwayne resource/username availability...)</li>
</ul>

This should generate:

<ul>
<li>200: if resource exists</li>
<li>404: if the resource does not exist</li>
</ul>

The second one seems more like "SOAP"-like web service, where you define a "function" (/users/search/) with some "parameters" (username, email)...

blocks|key|442760|text|对于唯一字段，第一个选项很适合(/users/email或/users/username/)，对于非唯一字段，搜索可能更合适。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|442761|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

For unique fields, first option is a good fit (/users/email or /users/username/), for non-unique fields search would be more appropriate.

blocks|key|2759074|text|我建议你使用HEAD+request而不是GET。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2759075|使用GET可能会带来安全问题。黑客可以使用组合来识别有效的用户名，因为GET将导致200或404。|2759076|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

i would recommend, you use HEAD request instead of GET.

Using a GET may pose a security problem. A hacker can use a combination to identify valid username as GET would either result in 200 or 404.

blocks|key|442812|text|您应该尝试通过以下方式获取邮件中的用户列表|type|unstyled|depth|inlineStyleRanges|entityRanges|data|442813|GET+/users?query=asd@gmail.com|code-block|syntax|javascript|442814|在这里你可以找到1个项目或0个项目。在第一种情况下，地址不是唯一的。在另一个地方-它是独一无二的|442815|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

You should try to get a list of users with your mail by 

<pre><code>GET /users?query=asd@gmail.com
</code></pre>

And here you can find 1 item or 0 items. In first case the address isn't unique. In another - it's unique

I've recently gotten very into trying to think as RESTfully as possible, and I'm finding myself stymied by the non-obvious routes.

In this particular case, I'm curious about the RESTful way to check for username and email availability for a user, or anything else that has uniqueness.

My gut tells me that I would want to perform a <code>GET</code> on <code>/users/email</code> or <code>/users/username/</code> each with a required param, or something along the lines of <code>GET /users/search/</code> with optional params of <code>email</code> and <code>username</code>. If you get a <code>200</code>, then the <code>username</code> or <code>email</code> is unavailable; if you get a <code>404</code>, then it's available.

I prefer the first option since it's more explicit, but it's not like I've pored over Roy Fielding's thesis to know well enough what to do.

What's the most sound approach here?

RESTful way to check availability of usernames, emails, etc

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我最近非常着迷于尽可能多地考虑RESTfully，我发现自己被不明显的路线所阻碍。在这个特殊的例子中，我对RESTful检查用户名和电子邮件可用性的方式很好奇，或者其他任何具有唯一性的东西。我的直觉告诉我，我会想要在/users/email或/users/username/上执行一个GET，每个都有一个必需的参数，或者...

问检查用户名、电子邮件等可用性的RESTful方法
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问检查用户名、电子邮件等可用性的RESTful方法EN