匿名使用者
匿名使用者 發問時間: 社會與文化語言 · 1 0 年前

英翻中,電腦相關的英語。(15點)

感恩~我從 but then 開始後就不大懂了。

Also, in the long term, you may find that using "Order Deny,Allow" will allow more flexibility. For example, you can "Deny from" many IP addresses, but then provide for an Allow that will override those Denies if your custom 403 error page is requested.

If you don't do that, then you can't even use a custom 403 page, because any attempt to serve it in response to a denied request would result in a second 403 error, and that second 403 error would cause a third -- and this would continue until either the client or the server detected the loop and gave up.

1 個解答

評分
  • 1 0 年前
    最佳解答

    這像似網頁程式的設定說明吧?

    Also, in the long term, you may find that using "Order Deny,Allow" will allow more flexibility. For example, you can "Deny from" many IP addresses, but then provide for an Allow that will override those Denies if your custom 403 error page is requested.

    而且,長期來說,你將發現若使用「拒絕/允許指令」將變得太有彈性,例如,你可以使用「拒絕來自於...指令」擋掉許多IP位址(讓它們進不來),但是你若設定「403錯誤訊息頁」,卻又等同「允許」那些已被「拒絕」的IP位址又能進入你的網站了!

    custom 403 error:403錯誤訊息頁,當無法連結上網時會出現的錯誤訊息頁面。

    If you don't do that, then you can't even use a custom 403 page, because any attempt to serve it in response to a denied request would result in a second 403 error, and that second 403 error would cause a third -- and this would continue until either the client or the server detected the loop and gave up.

    如果你不這麼做(設定403錯誤訊息頁),則連你自己也都不能使用(連結到)「403錯誤訊息頁」了。因為對一個已經回應「拒絕要求」的伺服器來說,任何登入的企圖都會產生第二次「403錯誤訊息」,而這第二次「403錯誤訊息」又會引發第三次「403錯誤訊息」,這個狀況將持續成一個無限回圈,直到使用者(client)或伺服器(server)發現並放棄(登入與提供登入服務)

還有問題?馬上發問,尋求解答。