为提升您的使用体验,本站正在维护,部分功能暂时无法使用。如果本站文章无法解决您的问题,您想要向社区提问的话,请到 Twitter 上的 @FirefoxSupport 或 Reddit 上的 /r/firefox 提问,我们的支持社区将会很快回复您的疑问。

搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

gives error The requested URL "/", is invalid but I gave a valid format

  • 5 个回答
  • 99 人有此问题
  • 1 次查看
  • 最后回复者为 robeyw

more options

I gave firefox 3.6.6 what I think is a properly formatted URL, namely http://www.3dfx.com. Firefox changes this to http://www.3dfx.com/ I think the added / indicates it got a response from the URL I gave but then it says The requested URL "/", is invalid.

Reference #9.eb4a595.1295368725.9366789

so it seems like it did not understand the format. By comparison, I enter http://www.purdue.edu and it is changed to http://www.purdue.edu/ and the page is displayed.

I gave firefox 3.6.6 what I think is a properly formatted URL, namely http://www.3dfx.com. Firefox changes this to http://www.3dfx.com/ I think the added / indicates it got a response from the URL I gave but then it says The requested URL "/", is invalid. Reference #9.eb4a595.1295368725.9366789 so it seems like it did not understand the format. By comparison, I enter http://www.purdue.edu and it is changed to http://www.purdue.edu/ and the page is displayed.

被采纳的解决方案

~ I HAD THE SAME PROBLEMS WITH MY NETFLIX QUEUE & WITH PAGES LOADING ON NETFLIX. WHEREAS I WOULD ALWAYS GET A BLANK PAGE WITH THE MESSAGE "URL...NOT FOUND" OR "URL....INVALID". ~ IT TURNS OUT IT MAY BE YOUR BROWSER'S NETWORK CONNECTION SETTING WHICH SHOULD BE CHECKED "AUTODETECT PROXY SETTINGS FOR THIS CONNECTION"

~ IN MOZILLA FOX GO TO "MENU" --> "TOOLS" --> OPTIONS --> ADVANCED --> NETWORK --> "CONNNECTION" --> "SETTINGS" --> THEN CHECK "AUTODETECT PROXY SETTINGS FOR THIS NETWORK"

~ HOPE IT WORKS FOR YOU LIKE IT DID FOR ME

定位到答案原位置 👍 4

所有回复 (5)

more options

That site no longer seems to exist, so you will have to use Google to find an alternative.

more options

Not being able to find the site should give a not found error, not "/ is invalid". Where would one look up Reference #9.eb4a595.1295368725.9366789 ?

more options

Here's a (maybe THE) solution, assuming you have the HTTPS Everywhere add-on installed. If not, then this will probably be of no help at all (sorry).

I was having this exact issue, only when attempting to reach the Washington Post website, which had always worked for me without problems before. I received this error message:

         The requested URL "/", is invalid.

To make matters even more confusing, I could reach the desired web site (using the same URL--http://www.washingtonpost.com) on the same PC using Internet Explorer, and on another PC using Firefox.

After an annoying search, Googling this error message, and trying a variety of suggested remedies, I was finally able to resolve the problem by changing the settings for the Firefox add-on HTTPS Everywhere.

In Firefox, click on the Tools menu, then select Add-ons, then click on HTTPS Everywhere and click on the Options button. The HTTPS Everywhere Preferences screen will appear asking, "Which HTTPS redirection rules should apply?"

Uncheck the website you're having the problem with and click OK. That should solve the problem. At least, for me it ended the problem immediately, without restarting Firefox, my PC, my router, or any of the other "remedies" I had tried during my earlier troubleshooting efforts.

由melraff于修改

more options

选择的解决方案

~ I HAD THE SAME PROBLEMS WITH MY NETFLIX QUEUE & WITH PAGES LOADING ON NETFLIX. WHEREAS I WOULD ALWAYS GET A BLANK PAGE WITH THE MESSAGE "URL...NOT FOUND" OR "URL....INVALID". ~ IT TURNS OUT IT MAY BE YOUR BROWSER'S NETWORK CONNECTION SETTING WHICH SHOULD BE CHECKED "AUTODETECT PROXY SETTINGS FOR THIS CONNECTION"

~ IN MOZILLA FOX GO TO "MENU" --> "TOOLS" --> OPTIONS --> ADVANCED --> NETWORK --> "CONNNECTION" --> "SETTINGS" --> THEN CHECK "AUTODETECT PROXY SETTINGS FOR THIS NETWORK"

~ HOPE IT WORKS FOR YOU LIKE IT DID FOR ME

more options

I have no idea what the problem was. As far as I know none of the suggestions applied in my case. It only occurred with the URL mentioned and now there is a new site there so the problem does not occur now.