Skip to main content

Bug Tracker

Side navigation

#8927 closed bug (invalid)

Opened April 20, 2011 07:17PM UTC

Closed May 05, 2011 07:52AM UTC

Last modified April 12, 2012 05:40PM UTC

.load() causes security warning in IE7/8 when loading only a fragment from target page

Reported by: jon_brockman Owned by: jon_brockman
Priority: low Milestone:
Component: ajax Version: 1.5.2
Keywords: Cc:
Blocked by: Blocking:

jquery 1.5.2

Windows XP

This affects only IE7 and IE8. Other browsers tested such as FF 4, Chrome 12 (dev), IE9 (on Windows 7) were unaffected.

If there are two pages, Foo.html and Bar.html, both on the same domain and both using https, the .load() function operates correctly and without any mixed content warning if loading the entirety of Bar into Foo.

However, if a fragment of the target page is being loaded, a mixed security warning is generated.

URls for reference:

Example (in Foo.html)


However, if loading a fragment from Bar.html, IE7 and IE8 throw the mixed security warning.

Example (in Foo.html)

$('#content').load(' #fragmentToLoad');

Unfortunately I cannot provide a working example as the two resources are not publicly available.

Attachments (0)
Change History (4)

Changed April 20, 2011 07:19PM UTC by jon_brockman comment:1

apologies, both load() calls should be to the same production URL.

Changed April 20, 2011 07:48PM UTC by timmywil comment:2

component: unfiledajax
owner: → jon_brockman
priority: undecidedlow
status: newpending

Thanks for taking the time to contribute to the jQuery project! Please provide a reduced test case that reproduces the issue experienced to help us assess your ticket.

Changed May 05, 2011 07:52AM UTC by trac-o-bot comment:3

resolution: → invalid
status: pendingclosed

Because we get so many tickets, we often need to return them to the initial reporter for more information. If that person does not reply within 14 days, the ticket will automatically be closed, and that has happened in this case. If you still are interested in pursuing this issue, feel free to add a comment with the requested information and we will be happy to reopen the ticket if it is still valid. Thanks!

Changed April 12, 2012 05:40PM UTC by comment:4


I have exactly the same problem.

Here's the URL of a website we have that has the same problem discussed above: