Bug Tracker

Modify

Ticket #9799 (closed enhancement: invalid)

Opened 23 months ago

Last modified 22 months ago

"/a" in jQuery.support causing 404's.

Reported by: simonkurtz@… Owned by: simonkurtz@…
Priority: low Milestone: 1.next
Component: support Version: 1.6.2
Keywords: Cc:
Blocking: Blocked by:

Description

If I understand correctly, jQuery.support checks for hrefNormalized (line 1174) to ensure what is placed in an a-tag's href attribute is also what is retrieved. I understand that IE may alter that to return a full URL rather than just the href attrib in itself.

It appears that somehow requests are made to this as we see 404s to "www.foo.com/a". If this "link" simply exists to check for hrefNormalized, would it make sense to add a 'rel="nofollow"' in the a-tag? I may not understand the situation entirely, but that seemed plausible to me.

Many thanks for a reply.

Change History

comment:1 Changed 23 months ago by ajpiano

  • Owner set to simonkurtz@…
  • Status changed from new to pending

Thanks for taking the time to contribute to the jQuery project! Please provide a reduced jsFiddle test case to help us assess your ticket! Additionally, be sure to test against the jQuery Edge version to ensure the issue still exists. To get you started, we've created this boilerplate:  http://jsfiddle.net/rwaldron/da3nM/ Open the link and click to "Fork" in the top menu.

comment:2 Changed 23 months ago by anonymous

Hi ajpiano,

I don't believe I can easily recreate as the dependency is a crawler or agent. For instance, we use Keynote monitoring for system availability, and a request to "/a" is something they actually have to exclude from their testing in order not to throw 404s. I'm sorry I am unable to provide more detail, but perhaps there are others in the community, who have run into this.

comment:3 Changed 23 months ago by timmywil

  • Priority changed from undecided to low
  • Component changed from unfiled to support
  • Milestone changed from None to 1.next

comment:4 Changed 22 months ago by trac-o-bot

  • Status changed from pending to closed
  • Resolution set to invalid

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!

Please follow the  bug reporting guidlines and use  jsFiddle when providing test cases and demonstrations instead of pasting the code in the ticket.

View

Add a comment

Modify Ticket

Action
as closed
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.