[{"_1":2,"_1004":-5,"_1005":-5},"loaderData",{"_3":4,"_53":54},"root",{"_5":6},"clerkState",{"_7":8},"__internal_clerk_state",{"_9":10,"_25":26,"_27":28,"_29":28,"_30":24,"_31":28,"_32":28,"_33":28,"_34":28,"_35":28,"_36":28,"_37":28,"_38":28,"_39":40,"_49":28,"_50":28,"_51":24,"_52":24},"__clerk_ssr_state",{"_11":12,"_13":-5,"_14":-5,"_15":-5,"_16":-5,"_17":-5,"_18":-5,"_19":-5,"_20":-5,"_21":-5,"_22":-5,"_23":24},"tokenType","session_token","sessionClaims","sessionId","sessionStatus","userId","actor","orgId","orgRole","orgSlug","orgPermissions","factorVerificationAge","isAuthenticated",false,"__publishableKey","pk_live_Y2xlcmsucXVlc3Rpb25zLnZpc3VhbGl6ZWl0LmFwcCQ","__proxyUrl","","__domain","__isSatellite","__signInUrl","__signUpUrl","__afterSignInUrl","__afterSignUpUrl","__signInForceRedirectUrl","__signUpForceRedirectUrl","__signInFallbackRedirectUrl","__signUpFallbackRedirectUrl","__clerk_debug",{"_41":24,"_23":24,"_42":28,"_43":44,"_45":28,"_46":26,"_47":24,"_48":28},"isSignedIn","proxyUrl","reason","session-token-and-uat-missing","message","publishableKey","isSatellite","domain","__clerkJSUrl","__clerkJSVersion","__telemetryDisabled","__telemetryDebug","routes/_index",{"_55":56,"_1000":1001},"questions",[57,196,235,264,296,320,343,367,396,425,449,473,508,532,556,580,611,635,659,683,707,731,755,778,802,825,849,873,897,928,952,976],{"_58":59,"_60":61,"_62":63,"_64":65,"_66":67,"_68":69,"_70":71,"_72":73,"_74":75,"_76":77,"_78":79,"_111":112,"_131":132,"_133":24,"_134":-5,"_135":136,"_137":138,"_159":152,"_153":160,"_155":161,"_158":-5,"_162":163,"_106":-5,"_164":-5,"_165":166,"_170":171,"_176":177,"_178":179,"_190":191,"_192":-5,"_193":-5,"_194":195},"url","https://api.github.com/repos/pro-collection/interview-question/issues/359","repository_url","https://api.github.com/repos/pro-collection/interview-question","labels_url","https://api.github.com/repos/pro-collection/interview-question/issues/359/labels{/name}","comments_url","https://api.github.com/repos/pro-collection/interview-question/issues/359/comments","events_url","https://api.github.com/repos/pro-collection/interview-question/issues/359/events","html_url","https://github.com/pro-collection/interview-question/issues/359","id",1712246502,"node_id","I_kwDOJGDC6c5mDs7m","number",359,"title","DNS解析过程","user",{"_80":81,"_70":82,"_72":83,"_84":85,"_86":28,"_58":87,"_68":88,"_89":90,"_91":92,"_93":94,"_95":96,"_97":98,"_99":100,"_101":102,"_66":103,"_104":105,"_106":107,"_108":109,"_110":24},"login","yanlele",22188674,"MDQ6VXNlcjIyMTg4Njc0","avatar_url","https://avatars.githubusercontent.com/u/22188674?v=4","gravatar_id","https://api.github.com/users/yanlele","https://github.com/yanlele","followers_url","https://api.github.com/users/yanlele/followers","following_url","https://api.github.com/users/yanlele/following{/other_user}","gists_url","https://api.github.com/users/yanlele/gists{/gist_id}","starred_url","https://api.github.com/users/yanlele/starred{/owner}{/repo}","subscriptions_url","https://api.github.com/users/yanlele/subscriptions","organizations_url","https://api.github.com/users/yanlele/orgs","repos_url","https://api.github.com/users/yanlele/repos","https://api.github.com/users/yanlele/events{/privacy}","received_events_url","https://api.github.com/users/yanlele/received_events","type","User","user_view_type","public","site_admin","labels",[113,124],{"_70":114,"_72":115,"_58":116,"_117":118,"_119":120,"_121":24,"_122":123},5232529101,"LA_kwDOJGDC6c8AAAABN-IOzQ","https://api.github.com/repos/pro-collection/interview-question/labels/%E7%BD%91%E7%BB%9C","name","网络","color","1A8829","default","description","web 网络相关",{"_70":125,"_72":126,"_58":127,"_117":128,"_119":129,"_121":24,"_122":130},5312738037,"LA_kwDOJGDC6c8AAAABPKny9Q","https://api.github.com/repos/pro-collection/interview-question/labels/%E7%99%BE%E5%BA%A6","百度","ededed","公司标签","state","open","locked","assignee","assignees",[],"milestone",{"_58":139,"_68":140,"_62":141,"_70":142,"_72":143,"_74":144,"_76":145,"_122":146,"_147":148,"_149":150,"_151":152,"_131":132,"_153":154,"_155":156,"_157":-5,"_158":-5},"https://api.github.com/repos/pro-collection/interview-question/milestones/3","https://github.com/pro-collection/interview-question/milestone/3","https://api.github.com/repos/pro-collection/interview-question/milestones/3/labels",9124547,"MI_kwDOJGDC6c4AizrD",3,"高","高级别面试问题","creator",{"_80":81,"_70":82,"_72":83,"_84":85,"_86":28,"_58":87,"_68":88,"_89":90,"_91":92,"_93":94,"_95":96,"_97":98,"_99":100,"_101":102,"_66":103,"_104":105,"_106":107,"_108":109,"_110":24},"open_issues",454,"closed_issues",0,"created_at","2023-03-06T15:00:27Z","updated_at","2025-09-07T06:21:17Z","due_on","closed_at","comments","2023-05-16T15:21:41Z","2023-05-16T15:21:42Z","author_association","MEMBER","active_lock_reason","sub_issues_summary",{"_167":152,"_168":152,"_169":152},"total","completed","percent_completed","issue_dependencies_summary",{"_172":152,"_173":152,"_174":152,"_175":152},"blocked_by","total_blocked_by","blocking","total_blocking","body","DNS（Domain Name System，域名系统）解析是将域名转换为对应的IP地址的过程。下面是DNS解析的一般步骤：\n\n1. 用户输入域名：用户在浏览器或其他应用程序中输入要访问的域名，例如 \"[www.example.com\"。](http://www.example.com%22%E3%80%82)\n\n2. 本地缓存查找：操作系统首先会检查本地的DNS缓存，看是否已经缓存了该域名的IP地址。如果有匹配的缓存记录，且仍在有效期内，将直接返回对应的IP地址。\n\n3. 本地域名服务器查询：如果本地缓存中没有找到对应的IP地址，操作系统会向配置的本地域名服务器（通常由ISP提供）发送查询请求。本地域名服务器是存储了大量DNS记录的服务器，通常可以快速响应查询请求。\n\n4. 递归查询或迭代查询：本地域名服务器接收到查询请求后，会根据自身的配置进行递归查询或迭代查询。\n\n * 递归查询：本地域名服务器会代表客户端进行完整的查询过程，直到找到目标域名的IP地址。如果本地域名服务器已经缓存了目标域名的IP地址，它将直接返回结果给客户端。\n\n * 迭代查询：本地域名服务器向根域名服务器发送查询请求，根域名服务器返回顶级域名服务器（TLD）的地址。然后本地域名服务器再向TLD发送查询请求，TLD返回该域名的授权域名服务器的地址。最后，本地域名服务器向授权域名服务器发送查询请求，授权域名服务器返回目标域名的IP地址。\n\n5. 返回IP地址：经过递归或迭代查询后，本地域名服务器会将获取到的IP地址返回给操作系统，然后操作系统将该IP地址存储在本地DNS缓存中，并将IP地址传递给应用程序。\n\n6. 应用程序访问目标IP地址：应用程序收到IP地址后，可以直接使用该IP地址与目标服务器建立连接，并进行相应的网络请求。\n\nDNS解析过程中还涉及到DNS记录的缓存、DNS服务器层级结构、域名的分级管理等概念和机制，以保证高效的解析过程和互联网的正常运行。","reactions",{"_58":180,"_181":152,"_182":152,"_183":152,"_184":152,"_185":152,"_186":152,"_187":152,"_188":152,"_189":152},"https://api.github.com/repos/pro-collection/interview-question/issues/359/reactions","total_count","+1","-1","laugh","hooray","confused","heart","rocket","eyes","timeline_url","https://api.github.com/repos/pro-collection/interview-question/issues/359/timeline","performed_via_github_app","state_reason","score",1,{"_58":197,"_60":61,"_62":198,"_64":199,"_66":200,"_68":201,"_70":202,"_72":203,"_74":204,"_76":205,"_78":206,"_111":207,"_131":132,"_133":24,"_134":-5,"_135":214,"_137":215,"_159":152,"_153":228,"_155":228,"_158":-5,"_162":163,"_106":-5,"_164":-5,"_165":229,"_170":230,"_176":231,"_178":232,"_190":234,"_192":-5,"_193":-5,"_194":195},"https://api.github.com/repos/pro-collection/interview-question/issues/335","https://api.github.com/repos/pro-collection/interview-question/issues/335/labels{/name}","https://api.github.com/repos/pro-collection/interview-question/issues/335/comments","https://api.github.com/repos/pro-collection/interview-question/issues/335/events","https://github.com/pro-collection/interview-question/issues/335",1697792612,"I_kwDOJGDC6c5lMkJk",335,"HTTP 304 状态码表达的请求过程是什么【热度: 459】",{"_80":81,"_70":82,"_72":83,"_84":85,"_86":28,"_58":87,"_68":88,"_89":90,"_91":92,"_93":94,"_95":96,"_97":98,"_99":100,"_101":102,"_66":103,"_104":105,"_106":107,"_108":109,"_110":24},[208,209],{"_70":114,"_72":115,"_58":116,"_117":118,"_119":120,"_121":24,"_122":123},{"_70":210,"_72":211,"_58":212,"_117":213,"_119":129,"_121":24,"_122":130},5312231007,"LA_kwDOJGDC6c8AAAABPKI2Xw","https://api.github.com/repos/pro-collection/interview-question/labels/%E9%98%BF%E9%87%8C%E5%B7%B4%E5%B7%B4","阿里巴巴",[],{"_58":216,"_68":217,"_62":218,"_70":219,"_72":220,"_74":221,"_76":222,"_122":223,"_147":224,"_149":225,"_151":152,"_131":132,"_153":226,"_155":227,"_157":-5,"_158":-5},"https://api.github.com/repos/pro-collection/interview-question/milestones/2","https://github.com/pro-collection/interview-question/milestone/2","https://api.github.com/repos/pro-collection/interview-question/milestones/2/labels",9124545,"MI_kwDOJGDC6c4AizrB",2,"中","中级程序面试问题",{"_80":81,"_70":82,"_72":83,"_84":85,"_86":28,"_58":87,"_68":88,"_89":90,"_91":92,"_93":94,"_95":96,"_97":98,"_99":100,"_101":102,"_66":103,"_104":105,"_106":107,"_108":109,"_110":24},510,"2023-03-06T15:00:15Z","2025-09-07T06:08:31Z","2023-05-05T15:16:05Z",{"_167":152,"_168":152,"_169":152},{"_172":152,"_173":152,"_174":152,"_175":152},"**关键词**：304状态码、304请求过程、304过程、304请求\n\nHTTP 304 状态码是表示所请求的资源未修改，可以直接使用客户端缓存的版本。当客户端发送 GET 请求时，服务器会检查该资源的 ETag（实体标签）或 Last-Modified（最后修改时间）等信息，与客户端缓存中的相应信息进行比较。如果这些信息相同，则表示资源未发生更改，服务器返回 304 状态码，告诉客户端直接使用本地缓存的资源即可，无需重新下载，这样可以大大节省网络带宽和服务器资源消耗。\n\n下面是 HTTP 304 的具体过程：\n\n1. 客户端首先给服务器发送一个请求，该请求包含了一个 If-Modified-Since 或者 If-None-Match 字段，用来在服务器端判断访问的资源是否已经被修改过。\n\n2. 如果服务器端检查发现访问的资源没有发生改变，服务器就不会发送资源内容，而是返回 304 的状态码给客户端。\n\n3. 客户端接收到 304 的状态码后，会从本地缓存中加载相应的资源。\n\n4. 如果服务器端发现访问的资源已经发生过改变，服务器会发送新的资源内容给客户端，并且返回 200 的状态码。\n\n需要注意的是，客户端缓存中的资源不一定完全等同于服务器端的资源，可能由于缓存失效等原因导致客户端缓存中的资源与服务器端不完全一致，因此在实际应用中，需要谨慎使用 304 缓存机制，尤其对于那些变化频繁的资源，建议设置较短的缓存时间，以避免出现缓存失效等问题。\n",{"_58":233,"_181":152,"_182":152,"_183":152,"_184":152,"_185":152,"_186":152,"_187":152,"_188":152,"_189":152},"https://api.github.com/repos/pro-collection/interview-question/issues/335/reactions","https://api.github.com/repos/pro-collection/interview-question/issues/335/timeline",{"_58":236,"_60":61,"_62":237,"_64":238,"_66":239,"_68":240,"_70":241,"_72":242,"_74":243,"_76":244,"_78":245,"_111":246,"_131":132,"_133":24,"_134":-5,"_135":253,"_137":254,"_159":152,"_153":256,"_155":257,"_158":-5,"_162":163,"_106":-5,"_164":-5,"_165":258,"_170":259,"_176":260,"_178":261,"_190":263,"_192":-5,"_193":-5,"_194":195},"https://api.github.com/repos/pro-collection/interview-question/issues/333","https://api.github.com/repos/pro-collection/interview-question/issues/333/labels{/name}","https://api.github.com/repos/pro-collection/interview-question/issues/333/comments","https://api.github.com/repos/pro-collection/interview-question/issues/333/events","https://github.com/pro-collection/interview-question/issues/333",1696365891,"I_kwDOJGDC6c5lHH1D",333,"TCP/IP 如何保证数据包传输的有序可靠【热度: 336】",{"_80":81,"_70":82,"_72":83,"_84":85,"_86":28,"_58":87,"_68":88,"_89":90,"_91":92,"_93":94,"_95":96,"_97":98,"_99":100,"_101":102,"_66":103,"_104":105,"_106":107,"_108":109,"_110":24},[247,248],{"_70":114,"_72":115,"_58":116,"_117":118,"_119":120,"_121":24,"_122":123},{"_70":249,"_72":250,"_58":251,"_117":252,"_119":129,"_121":24,"_122":130},5312726360,"LA_kwDOJGDC6c8AAAABPKnFWA","https://api.github.com/repos/pro-collection/interview-question/labels/%E8%85%BE%E8%AE%AF","腾讯",[],{"_58":139,"_68":140,"_62":141,"_70":142,"_72":143,"_74":144,"_76":145,"_122":146,"_147":255,"_149":150,"_151":152,"_131":132,"_153":154,"_155":156,"_157":-5,"_158":-5},{"_80":81,"_70":82,"_72":83,"_84":85,"_86":28,"_58":87,"_68":88,"_89":90,"_91":92,"_93":94,"_95":96,"_97":98,"_99":100,"_101":102,"_66":103,"_104":105,"_106":107,"_108":109,"_110":24},"2023-05-04T16:58:10Z","2023-05-04T16:58:11Z",{"_167":152,"_168":152,"_169":152},{"_172":152,"_173":152,"_174":152,"_175":152},"**关键词**：TCP/IP 可靠性、TCP/IP 序列号、TCP/IP 超时\n\nTCP/IP 采用以下几种机制来保证数据包传输的有序可靠：\n\n1. 确认和重传：每当 TCP/IP 协议收到一个数据包时，将向发送方回送一个确认信息。如果接收方未收到数据包，则发送方将重传该数据包。这种确认和重传的机制可以确保数据包能够可靠地传输，即使在网络故障或拥塞的情况下也能保证数据包的可靠性。\n\n2. 滑动窗口：滑动窗口是 TCP/IP 协议用来控制发送方和接收方之间数据流的一种机制。发送方会将窗口大小告知接收方，接收方在收到数据包时，会回送一个告知发送方可以继续发送数据的指令。滑动窗口机制可以通过有效地控制数据包的发送与接收，实现有序的数据传输。\n\n3. 序列号：每个数据包都会附带一个序列号，接收方通过序列号对数据包进行排序，从而实现传输的有序性。\n\n4. 超时重传时间：TCP/IP 建立了一个计时器，如果在指定时间内没有收到确认信息，则会重新发送未确认的数据包。这种机制可以帮助保证数据包传输的可靠性，确保数据包能够及时被送达。\n\n总之，TCP/IP 协议通过确认和重传、滑动窗口、序列号以及超时重传时间等机制，保证了数据包传输的有序可靠性。这些机制可以确保数据包能够被及时送达，有效地防止了数据包丢失、重复和乱序等问题，从而提供了高效可靠的传输服务。\n",{"_58":262,"_181":152,"_182":152,"_183":152,"_184":152,"_185":152,"_186":152,"_187":152,"_188":152,"_189":152},"https://api.github.com/repos/pro-collection/interview-question/issues/333/reactions","https://api.github.com/repos/pro-collection/interview-question/issues/333/timeline",{"_58":265,"_60":61,"_62":266,"_64":267,"_66":268,"_68":269,"_70":270,"_72":271,"_74":272,"_76":273,"_78":274,"_111":275,"_131":132,"_133":24,"_134":-5,"_135":285,"_137":286,"_159":152,"_153":288,"_155":289,"_158":-5,"_162":163,"_106":-5,"_164":-5,"_165":290,"_170":291,"_176":292,"_178":293,"_190":295,"_192":-5,"_193":-5,"_194":195},"https://api.github.com/repos/pro-collection/interview-question/issues/332","https://api.github.com/repos/pro-collection/interview-question/issues/332/labels{/name}","https://api.github.com/repos/pro-collection/interview-question/issues/332/comments","https://api.github.com/repos/pro-collection/interview-question/issues/332/events","https://github.com/pro-collection/interview-question/issues/332",1696353753,"I_kwDOJGDC6c5lHE3Z",332,"DNS 协议了解多少【热度: 712】",{"_80":81,"_70":82,"_72":83,"_84":85,"_86":28,"_58":87,"_68":88,"_89":90,"_91":92,"_93":94,"_95":96,"_97":98,"_99":100,"_101":102,"_66":103,"_104":105,"_106":107,"_108":109,"_110":24},[276,277,284],{"_70":114,"_72":115,"_58":116,"_117":118,"_119":120,"_121":24,"_122":123},{"_70":278,"_72":279,"_58":280,"_117":281,"_119":282,"_121":24,"_122":283},5312047129,"LA_kwDOJGDC6c8AAAABPJ9oGQ","https://api.github.com/repos/pro-collection/interview-question/labels/web%E5%BA%94%E7%94%A8%E5%9C%BA%E6%99%AF","web应用场景","EA4E1E","应用场景类问题",{"_70":249,"_72":250,"_58":251,"_117":252,"_119":129,"_121":24,"_122":130},[],{"_58":216,"_68":217,"_62":218,"_70":219,"_72":220,"_74":221,"_76":222,"_122":223,"_147":287,"_149":225,"_151":152,"_131":132,"_153":226,"_155":227,"_157":-5,"_158":-5},{"_80":81,"_70":82,"_72":83,"_84":85,"_86":28,"_58":87,"_68":88,"_89":90,"_91":92,"_93":94,"_95":96,"_97":98,"_99":100,"_101":102,"_66":103,"_104":105,"_106":107,"_108":109,"_110":24},"2023-05-04T16:50:50Z","2023-05-04T16:50:51Z",{"_167":152,"_168":152,"_169":152},{"_172":152,"_173":152,"_174":152,"_175":152},"**关键词**：DNS协议、DNS加速\n\n### DNS 基本概念 \n\nDNS（Domain Name System，域名系统）是因特网上用于将主机名转换为 IP 地址的协议。它是一个分布式数据库系统，通过将主机名映射到 IP 地址来实现主机名解析，并使用户能够通过更容易识别的主机名来访问互联网上的资源。\n\n在使用 DNS 协议进行主机名解析时，系统首先查询本地 DNS 缓存。如果缓存中不存在结果，系统将向本地 DNS 服务器发出请求，并逐级向上查找，直到找到权威 DNS 服务器并获得解析结果。在域名解析的过程中，DNS 协议采用了分级命名空间的结构，不同的域名可以通过点分隔符分为多个级别，例如 `www.example.com` 可以分为三个级别：`www`、`example` 和 `com`。\n\n除了将域名映射到 IP 地址之外，DNS 协议还支持多种其他功能：\n\n1. 逆向映射：将 IP 地址解析为域名。\n2. 邮件服务器设置：支持邮件服务器的自动发现和设置。\n3. 负载均衡：DNS 还可以实现简单的负载均衡，通过将相同 IP 地址的主机名映射到不同的 IP 地址来分散负载。\n4. 安全：DNSSEC（DNS Security Extensions，DNS 安全扩展）可以提供对域名解析的认证和完整性。\n\n### 如何加快 DNS 的解析？\n\n有以下几种方法可以加快 DNS 的解析：\n\n1. 使用高速 DNS 服务器：默认情况下，网络服务提供商（ISP）为其用户提供 DNS 服务器。但是，这些服务器不一定是最快的，有时会出现瓶颈。如果您想加快 DNS 解析，请尝试使用其他高速 DNS 服务器，例如 Google 的公共 DNS 服务器或 OpenDNS。\n\n2. 缓存 DNS 记录：在本地计算机上缓存 DNS 记录可以大大加快应用程序的响应。当您访问特定的网站时，计算机会自动缓存该网站的 DNS 记录。如果您再次访问该网站，则计算机将使用缓存的 DNS 记录。\n\n3. 减少 DNS 查找：当您访问一个网站时，您的计算机将会查找该域名的 IP 地址。如果网站有很多域名，则查找过程可能会变得非常缓慢。因此，尽可能使用较少的域名可以减少 DNS 查找的数量，并提高响应速度。\n\n4. 使用 CDN：CDN（内容分发网络）是一种将内容存储在全球多个位置的系统。这些位置通常都有专用的 DNS 服务器，可以大大加快站点的加载速度。\n\n5. 使用 DNS 缓存工具：一些辅助工具可以帮助您优化与 DNS 相关的设置，例如免费的 DNS Jumper 软件和 Namebench 工具，它们可以测试您的 DNS 响应时间并为您推荐最佳配置。\n\n通过使用高速 DNS 服务器、缓存 DNS 记录、减少 DNS 查找、使用 CDN 和 DNS 缓存工具等方法，可以显著提高 DNS 解析速度，从而加快应用程序响应时间。\n",{"_58":294,"_181":152,"_182":152,"_183":152,"_184":152,"_185":152,"_186":152,"_187":152,"_188":152,"_189":152},"https://api.github.com/repos/pro-collection/interview-question/issues/332/reactions","https://api.github.com/repos/pro-collection/interview-question/issues/332/timeline",{"_58":297,"_60":61,"_62":298,"_64":299,"_66":300,"_68":301,"_70":302,"_72":303,"_74":304,"_76":305,"_78":306,"_111":307,"_131":132,"_133":24,"_134":-5,"_135":309,"_137":310,"_159":152,"_153":312,"_155":313,"_158":-5,"_162":163,"_106":-5,"_164":-5,"_165":314,"_170":315,"_176":316,"_178":317,"_190":319,"_192":-5,"_193":-5,"_194":195},"https://api.github.com/repos/pro-collection/interview-question/issues/297","https://api.github.com/repos/pro-collection/interview-question/issues/297/labels{/name}","https://api.github.com/repos/pro-collection/interview-question/issues/297/comments","https://api.github.com/repos/pro-collection/interview-question/issues/297/events","https://github.com/pro-collection/interview-question/issues/297",1673437110,"I_kwDOJGDC6c5jvp-2",297,"CDN 了解多少？【热度: 413】",{"_80":81,"_70":82,"_72":83,"_84":85,"_86":28,"_58":87,"_68":88,"_89":90,"_91":92,"_93":94,"_95":96,"_97":98,"_99":100,"_101":102,"_66":103,"_104":105,"_106":107,"_108":109,"_110":24},[308],{"_70":114,"_72":115,"_58":116,"_117":118,"_119":120,"_121":24,"_122":123},[],{"_58":216,"_68":217,"_62":218,"_70":219,"_72":220,"_74":221,"_76":222,"_122":223,"_147":311,"_149":225,"_151":152,"_131":132,"_153":226,"_155":227,"_157":-5,"_158":-5},{"_80":81,"_70":82,"_72":83,"_84":85,"_86":28,"_58":87,"_68":88,"_89":90,"_91":92,"_93":94,"_95":96,"_97":98,"_99":100,"_101":102,"_66":103,"_104":105,"_106":107,"_108":109,"_110":24},"2023-04-18T16:05:14Z","2023-04-23T13:11:12Z",{"_167":152,"_168":152,"_169":152},{"_172":152,"_173":152,"_174":152,"_175":152},"### CDN 是什么\n\nCDN（Content Delivery Network）是指内容分发网络，它是由分布在不同地理位置的多台服务器组成的网络系统，用于更快地传递互联网内容和服务。CDN 可以缓存静态资源，加速用户访问速度，降低带宽消耗和服务器压力。\n\n1. CDN 的工作原理：CDN 通过将资源缓存在离用户更近的边缘节点，使用户可以更快地获取所需的内容。当用户访问一个包含 CDN 链接的网站时，CDN 会从最接近用户的节点返回内容。\n\n2. CDN 的优点：CDN 可以加速网站的加载速度、减轻源服务器的负载、提高网站的可用性和可靠性，同时还可以降低网络带宽使用和成本。\n\n3. CDN 的缓存策略：CDN 缓存可以采用不同的缓存策略，如时间戳策略、版本号策略、缓存控制策略等，以便尽可能地避免缓存出错或不及时更新。\n\n4. CDN 的常见问题：CDN 存在一些常见的问题，如缓存不一致、缓存雪崩、CDN 费用等。需要开发者和运维人员注意这些问题，并采取相应的解决方案。\n\n5. CDN 的选择：CDN 服务提供商众多，选择合适的 CDN 服务提供商需要考虑许多因素，如价格、性能、服务范围、支持的功能和协议等。\n\n6. CDN 的应用：CDN 被广泛应用于各种场景，如网站加速、视频点播、直播、在线游戏等。在实际应用中，需要根据具体场景来选择合适的 CDN 服务提供商和缓存策略，以达到最佳的效果。\n\n### CDN 预热\n\nCDN预热指在流量大涨之前，提前将资源缓存到CDN节点中，以加快用户请求响应速度，提高用户访问质量和稳定性的一种行为。通过提前将内容分发到CDN节点上，可以减少用户访问时由于第一次请求资源而导致的等待时间，从而提升用户的体验感受。一般来说，CDN预热是指在特定时间（如发布活动、重要通知等）前对资源进行CDN缓存的操作。预热完成后，用户请求相关资源时，就可以直接从CDN节点获取资源，而无需请求源站，从而提高网站的访问速度和稳定性。\n\n### CDN 刷新是什么\n\nCDN刷新指的是CDN缓存中的文件被更新后，需要将CDN服务器上缓存的旧文件清除，让其重新从源站拉取最新的内容，以保证CDN上的文件与源站文件保持一致。\n\n在网站更新或修改静态资源文件后，如果用户再次请求该文件，CDN服务器上的缓存仍然是旧版本的，用户就会访问到过时的文件，影响用户体验。为了解决这个问题，CDN提供了刷新服务，即将缓存的旧版本强制失效，让用户请求时可以快速访问到更新后的最新版本。\n\nCDN刷新通常有两种方式：\n\n1. 目录刷新：将某个目录下的所有文件都刷新，比较适用于网站进行大规模更新。\n\n2. 文件刷新：只将某个具体的文件刷新，比较适用于紧急情况下需要快速更新某个文件的情况。但由于刷新一次需要一定时间，因此刷新频率需要控制在合理的范围内，以避免影响CDN服务器性能和稳定性。\n\n### CDN 缓存策略有哪些\n\nCDN 缓存策略指的是在 CDN 服务器上缓存哪些资源以及缓存的有效期等相关规则。常见的 CDN 缓存策略有以下几种：\n\n1. 强制缓存：在资源的有效期内，浏览器每次请求该资源时，都直接从浏览器缓存中获取，不发送请求到服务器。可以通过设置响应头的 Cache-Control 和 Expires 字段实现。\n\n2. 协商缓存：在资源的有效期过期后，浏览器向服务器发起请求，并通过 If-Modified-Since 或者 If-None-Match 等字段验证资源是否有更新。如果资源未更新，服务器返回 304 Not Modified 响应，浏览器直接从本地缓存中获取资源。可以通过设置响应头的 Last-Modified 和 ETag 字段实现。\n\n3. CDN 边缘缓存：CDN 服务器缓存来自源站的资源，并将其分发给全球各地的用户。当用户请求某个资源时，CDN 服务器会根据缓存策略判断是否需要重新向源站请求资源。常见的缓存策略包括时间戳缓存、版本号缓存、目录级别缓存、参数级别缓存等。\n\n4. 客户端缓存：客户端缓存是指浏览器在本地缓存响应资源，下次请求该资源时可以直接从本地获取。可以通过设置响应头的 Cache-Control 和 Expires 字段实现。\n\n5. 源站缓存：源站缓存是指将静态资源放到应用服务器上缓存，在应用服务器上缓存的时间要短于 CDN 边缘缓存的时间。当 CDN 服务器的缓存过期或者未命中时，CDN 服务器会向源站发起请求获取最新的资源，并将其缓存到 CDN 服务器上。\n\n\n### 参考文档\n- https://juejin.cn/post/6913704568325046279\n- https://juejin.cn/post/7064952956201730062\n- https://juejin.cn/post/7166782260933296142\n",{"_58":318,"_181":152,"_182":152,"_183":152,"_184":152,"_185":152,"_186":152,"_187":152,"_188":152,"_189":152},"https://api.github.com/repos/pro-collection/interview-question/issues/297/reactions","https://api.github.com/repos/pro-collection/interview-question/issues/297/timeline",{"_58":321,"_60":61,"_62":322,"_64":323,"_66":324,"_68":325,"_70":326,"_72":327,"_74":328,"_76":329,"_78":330,"_111":331,"_131":132,"_133":24,"_134":-5,"_135":333,"_137":334,"_159":152,"_153":336,"_155":336,"_158":-5,"_162":163,"_106":-5,"_164":-5,"_165":337,"_170":338,"_176":339,"_178":340,"_190":342,"_192":-5,"_193":-5,"_194":195},"https://api.github.com/repos/pro-collection/interview-question/issues/223","https://api.github.com/repos/pro-collection/interview-question/issues/223/labels{/name}","https://api.github.com/repos/pro-collection/interview-question/issues/223/comments","https://api.github.com/repos/pro-collection/interview-question/issues/223/events","https://github.com/pro-collection/interview-question/issues/223",1644213421,"I_kwDOJGDC6c5iALSt",223,"介绍下如何实现 token 加密？",{"_80":81,"_70":82,"_72":83,"_84":85,"_86":28,"_58":87,"_68":88,"_89":90,"_91":92,"_93":94,"_95":96,"_97":98,"_99":100,"_101":102,"_66":103,"_104":105,"_106":107,"_108":109,"_110":24},[332],{"_70":114,"_72":115,"_58":116,"_117":118,"_119":120,"_121":24,"_122":123},[],{"_58":139,"_68":140,"_62":141,"_70":142,"_72":143,"_74":144,"_76":145,"_122":146,"_147":335,"_149":150,"_151":152,"_131":132,"_153":154,"_155":156,"_157":-5,"_158":-5},{"_80":81,"_70":82,"_72":83,"_84":85,"_86":28,"_58":87,"_68":88,"_89":90,"_91":92,"_93":94,"_95":96,"_97":98,"_99":100,"_101":102,"_66":103,"_104":105,"_106":107,"_108":109,"_110":24},"2023-03-28T15:36:35Z",{"_167":152,"_168":152,"_169":152},{"_172":152,"_173":152,"_174":152,"_175":152},"Token 是一种常用的身份验证机制，通常被用于 Web 应用程序的用户身份验证。Token 的生成和使用可以使用加密技术来增强安全性，下面介绍一下如何实现 Token 加密。\n\nToken 加密一般有两个步骤：\n\n1. 生成 Token\n2. 加密 Token\n\n### 1. 生成 Token\n\n在生成 Token 时，需要将用户的一些信息进行组合，生成一个字符串，该字符串通常包括以下信息：\n\n1. 用户的唯一标识（如用户 ID）\n2. 时间戳\n3. 有效期\n\n这些信息可以用分隔符分隔开，如用“.”分隔。\n\n### 2. 加密 Token\n\n加密 Token 有多种方式，下面介绍两种常用的方式：\n\n#### 1. 对称加密\n\n对称加密是指加密和解密使用同一密钥的加密算法。对称加密的优点是加解密速度快，缺点是密钥传输容易被截获，从而影响安全性。\n\n常用的对称加密算法有 DES、3DES、AES 等。\n\n#### 2. 非对称加密\n\n非对称加密是指加密和解密使用不同密钥的加密算法。非对称加密的优点是密钥传输安全，缺点是加解密速度较慢。\n\n常用的非对称加密算法有 RSA、DSA 等。\n\n一般情况下，为了兼顾安全性和效率，通常采用混合加密，即先使用非对称加密算法对 Token 进行加密，再使用对称加密算法对加密后的 Token 进行加密。\n\n综上所述，实现 Token 加密的关键在于对 Token 的生成和加密，需要根据具体业务需求来选择合适的加密算法和加密方式。",{"_58":341,"_181":152,"_182":152,"_183":152,"_184":152,"_185":152,"_186":152,"_187":152,"_188":152,"_189":152},"https://api.github.com/repos/pro-collection/interview-question/issues/223/reactions","https://api.github.com/repos/pro-collection/interview-question/issues/223/timeline",{"_58":344,"_60":61,"_62":345,"_64":346,"_66":347,"_68":348,"_70":349,"_72":350,"_74":351,"_76":352,"_78":353,"_111":354,"_131":132,"_133":24,"_134":-5,"_135":356,"_137":357,"_159":195,"_153":359,"_155":360,"_158":-5,"_162":163,"_106":-5,"_164":-5,"_165":361,"_170":362,"_176":363,"_178":364,"_190":366,"_192":-5,"_193":-5,"_194":195},"https://api.github.com/repos/pro-collection/interview-question/issues/213","https://api.github.com/repos/pro-collection/interview-question/issues/213/labels{/name}","https://api.github.com/repos/pro-collection/interview-question/issues/213/comments","https://api.github.com/repos/pro-collection/interview-question/issues/213/events","https://github.com/pro-collection/interview-question/issues/213",1642380409,"I_kwDOJGDC6c5h5Lx5",213,"https 的证书验证过程是什么样的",{"_80":81,"_70":82,"_72":83,"_84":85,"_86":28,"_58":87,"_68":88,"_89":90,"_91":92,"_93":94,"_95":96,"_97":98,"_99":100,"_101":102,"_66":103,"_104":105,"_106":107,"_108":109,"_110":24},[355],{"_70":114,"_72":115,"_58":116,"_117":118,"_119":120,"_121":24,"_122":123},[],{"_58":216,"_68":217,"_62":218,"_70":219,"_72":220,"_74":221,"_76":222,"_122":223,"_147":358,"_149":225,"_151":152,"_131":132,"_153":226,"_155":227,"_157":-5,"_158":-5},{"_80":81,"_70":82,"_72":83,"_84":85,"_86":28,"_58":87,"_68":88,"_89":90,"_91":92,"_93":94,"_95":96,"_97":98,"_99":100,"_101":102,"_66":103,"_104":105,"_106":107,"_108":109,"_110":24},"2023-03-27T16:00:36Z","2023-09-16T16:59:45Z",{"_167":152,"_168":152,"_169":152},{"_172":152,"_173":152,"_174":152,"_175":152},"HTTPS的证书验证过程通常包括以下几个步骤：\n\n1. 客户端向服务端发起HTTPS请求，服务端将其公钥证书发送给客户端。\n2. 客户端接收到服务端的证书后，首先验证证书是否过期，如果过期，则证书无效，验证失败；如果证书未过期，则进行下一步。\n3. 客户端使用CA证书（如系统内置的或者从服务端获取）对服务端证书进行验证，以确定该证书是否是由受信任的CA颁发的。如果验证失败，则证书无效，验证失败；如果验证成功，则进行下一步。\n4. 客户端生成一个随机值，使用服务端公钥进行加密，并将加密后的随机值发送给服务端。\n5. 服务端接收到客户端的随机值后，使用私钥进行解密，得到随机值。服务端再将随机值作为密钥，使用对称加密算法加密需要传输的数据，并发送给客户端。\n6. 客户端接收到服务端发送的加密数据后，使用随机值进行解密，得到明文数据。\n\n以上就是HTTPS证书验证的一般流程。客户端验证服务端证书的方式是通过验证证书的数字签名来确定证书的合法性，如果数字签名验证失败，则证书无效，验证失败。",{"_58":365,"_181":152,"_182":152,"_183":152,"_184":152,"_185":152,"_186":152,"_187":152,"_188":152,"_189":152},"https://api.github.com/repos/pro-collection/interview-question/issues/213/reactions","https://api.github.com/repos/pro-collection/interview-question/issues/213/timeline",{"_58":368,"_60":61,"_62":369,"_64":370,"_66":371,"_68":372,"_70":373,"_72":374,"_74":375,"_76":376,"_78":377,"_111":378,"_131":132,"_133":24,"_134":-5,"_135":385,"_137":386,"_159":195,"_153":388,"_155":389,"_158":-5,"_162":163,"_106":-5,"_164":-5,"_165":390,"_170":391,"_176":392,"_178":393,"_190":395,"_192":-5,"_193":-5,"_194":195},"https://api.github.com/repos/pro-collection/interview-question/issues/206","https://api.github.com/repos/pro-collection/interview-question/issues/206/labels{/name}","https://api.github.com/repos/pro-collection/interview-question/issues/206/comments","https://api.github.com/repos/pro-collection/interview-question/issues/206/events","https://github.com/pro-collection/interview-question/issues/206",1640932956,"I_kwDOJGDC6c5hzqZc",206,"浏览器缓存中 Memory Cache 和 Disk Cache，有啥区别？",{"_80":81,"_70":82,"_72":83,"_84":85,"_86":28,"_58":87,"_68":88,"_89":90,"_91":92,"_93":94,"_95":96,"_97":98,"_99":100,"_101":102,"_66":103,"_104":105,"_106":107,"_108":109,"_110":24},[379,380],{"_70":114,"_72":115,"_58":116,"_117":118,"_119":120,"_121":24,"_122":123},{"_70":381,"_72":382,"_58":383,"_117":384,"_119":129,"_121":24,"_122":130},5312712328,"LA_kwDOJGDC6c8AAAABPKmOiA","https://api.github.com/repos/pro-collection/interview-question/labels/%E5%AD%97%E8%8A%82%E8%B7%B3%E5%8A%A8","字节跳动",[],{"_58":139,"_68":140,"_62":141,"_70":142,"_72":143,"_74":144,"_76":145,"_122":146,"_147":387,"_149":150,"_151":152,"_131":132,"_153":154,"_155":156,"_157":-5,"_158":-5},{"_80":81,"_70":82,"_72":83,"_84":85,"_86":28,"_58":87,"_68":88,"_89":90,"_91":92,"_93":94,"_95":96,"_97":98,"_99":100,"_101":102,"_66":103,"_104":105,"_106":107,"_108":109,"_110":24},"2023-03-26T14:24:33Z","2023-04-12T13:47:16Z",{"_167":152,"_168":152,"_169":152},{"_172":152,"_173":152,"_174":152,"_175":152},"### Memory Cache 和 Disk Cache 的区别\r\n\r\n在浏览器缓存中，Memory Cache 和 Disk Cache 是两种不同的缓存类型，它们有以下区别：\r\n\r\n1. 存储位置：Memory Cache 存储在内存中，而 Disk Cache 存储在硬盘中。\r\n2. 读取速度：Memory Cache 读取速度比 Disk Cache 快，因为内存访问速度比硬盘访问速度快。\r\n3. 存储容量：Memory Cache 存储容量比较小，一般只有几十兆，而 Disk Cache 存储容量比较大，可以有数百兆或者更多。\r\n4. 生命周期：Memory Cache 生命周期短暂，一般只在当前会话中有效，当会话结束或者浏览器关闭时，Memory Cache 就会被清空；而 Disk Cache 生命周期比较长，数据可以被保存很长时间，即使浏览器关闭了，下次打开还可以使用。\r\n\r\n一般来说，浏览器在请求资源时，会优先从 Memory Cache 中读取，如果没有找到再去 Disk Cache 中查找。如果两种缓存中都没有找到，则会向服务器发送请求。如果需要强制刷新缓存，可以通过清空浏览器缓存来实现。\r\n\r\n### 什么情况下资源会缓存在 Memory Cache，什么情况下会缓存在 Disk Cache ?\r\n\r\n浏览器中的缓存是为了提高网页访问速度和减少网络流量而存在的。缓存分为 Memory Cache 和 Disk Cache 两种。\r\n\r\nMemory Cache 是浏览器内存缓存，资源会被缓存在内存中，由于内存读取速度快，所以 Memory Cache 的读取速度也较快。资源被缓存在 Memory Cache 中的情况有：\r\n\r\n1. 当前页面中通过或者