Шукати в статтях підтримки

Остерігайтеся нападів зловмисників. Mozilla ніколи не просить вас зателефонувати, надіслати номер телефону у повідомленні або поділитися з кимось особистими даними. Будь ласка, повідомте про підозрілі дії за допомогою меню “Повідомити про зловживання”

Докладніше

Ця тема перенесена в архів. Якщо вам потрібна допомога, запитайте.

FF13.x Not Requesting Correct URL from IFrame SRC Attribute

  • 2 відповіді
  • 2 мають цю проблему
  • 1 перегляд
  • Остання відповідь від mavigozler

more options

Question text says it all.

I have an iframe element in my HTML file where the src attribute at first specified a relative path (src="../../index.html" or src="../../") to another HTML document. Then an absolute URL (src="http://localhost/path/to/index.html"). Firebug is reporting a 404, and the reason is that it the HTTP request is to an index file in the parent directory of the currently loaded document. No matter what is set in the src attribute, the HTTP request is for an index.html in the directory that is immediate parent of directory of currently loaded document.

This document works---iframe loaded and processed---as expected in latest IE version (other HTTP clients not tested yet). So it is any wonder why FF is doing this bizarre behavior.

Things done:

  • cache was cleared
  • cookies were cleared
  • FF run with adds-on disabled
  • googled for some bizarre security issue: should not be cross-domain problem
  • MDN page for iframe checked for deviations from element coding standard: none found, document validates, including the iframe-loaded one
  • considered, but could not think of some about:config setting where iframe requests only are to parent directory
  • screaming and cursing at the browser
Question text says it all. I have an '''iframe '''element in my HTML file where the '''src '''attribute at first specified a relative path ('''src="../../index.html"''' or''' src="../../"''') to another HTML document. Then an absolute URL ('''src="http://localhost/path/to/index.html"'''). '''Firebug '''is reporting a '''404''', and the reason is that it the HTTP request is to an index file in the '''parent directory''' of the currently loaded document. No matter what is set in the src attribute, the HTTP request is for an''''' index.html''''' in the directory that is immediate parent of directory of currently loaded document. This document works---iframe loaded and processed---as expected in''' latest IE version''' (other HTTP clients not tested yet). So it is any wonder why FF is doing this bizarre behavior. Things done: * cache was cleared * cookies were cleared * FF run with adds-on disabled * googled for some bizarre security issue: should not be cross-domain problem * MDN page for iframe checked for deviations from element coding standard: none found, document validates, including the iframe-loaded one * considered, but could not think of some about:config setting where iframe requests only are to parent directory * screaming and cursing at the browser

Змінено mavigozler

Обране рішення

You can open the Web Console (Web Developer > Web Console; Shift+Ctrl+K) to see if Firefox request the file(s) and inspect the response by clicking a Net entry in the list.

Does it work if you open such an URL directly in the location bar?

If that works then it is most likely a security problem.

See also:

Читати цю відповідь у контексті 👍 0

Усі відповіді (2)

more options

Вибране рішення

You can open the Web Console (Web Developer > Web Console; Shift+Ctrl+K) to see if Firefox request the file(s) and inspect the response by clicking a Net entry in the list.

Does it work if you open such an URL directly in the location bar?

If that works then it is most likely a security problem.

See also:

more options

I restarted the entire system and saw your reply later. When I opened the console, it had then indicated a 304 Not Modified and was finding the correct document for iframe load. Not sure what happened, but it's working now. Thanks.