50

Steps to reproduce:

  1. View results for C# tag

  2. Change sorting to "date posted"
  3. You will now see that your search criteria is for C, not C#.

  • 17
    Reproduced. Again, I'm confused by the downvote, but w/e. – Aza Oct 30 '13 at 5:55
  • What browser and OS are you using? I cannot repro on Chrome 30. – Juice Oct 30 '13 at 13:41
  • I'm on chrome 30 as well – Darren Kopp Oct 30 '13 at 13:44
  • 2
    Ah. I got it. It doesn't do that when you "search" for C#. You have to use the tags link. – Juice Oct 30 '13 at 13:56
  • Correct, only happens when browsing via tag – Darren Kopp Oct 30 '13 at 14:53
  • @Juice shameless bump... is this scheduled for a fix? :) (I know you can't fix it yourself yet but you can nudge those who can better than us mortals) – ShaWiz Feb 4 '14 at 7:56
  • 100 bounty? I'll give it another shot. – Nick Larsen Mar 6 '14 at 13:08
  • @NickLarsen Roberta was faster and will get the hard earned 100 as soon as I can grant it... fix confirmed so can you please tag this as status-completed? – ShaWiz Mar 6 '14 at 15:25
  • 2
    @ShadowWizard I'm Roberta's mentor! – Nick Larsen Mar 6 '14 at 17:44
  • 2
    @NickLarsen then you're a great mentor, she squashed that bug like... well, like a bug! :D – ShaWiz Mar 6 '14 at 18:30
11
+100

Thanks for the report. This issue has now been fixed.

It looks like there's a problem with Url.AbsolutePath, which was trimming 'c%23' into 'c'.

enter image description here

Changing it to Url.RawUrl did the trick.

  • 4
    Thanks, can you please mention you work for Stack Exchange in your profile though? And you can ask for a diamond here so you can tag such questions status-completed after you fix. :-) – ShaWiz Mar 6 '14 at 15:23
  • 2
    @Shadow Wizard just mentioned it in my profile. Diamond is on its way :) thanks! – rla4 Mar 6 '14 at 15:35
  • Are you sure the # was encoded? I'm not observing this behaviour when it's encoded (screenshot), while I do see this behaviour when it's not encoded (screenshot). – Stijn Mar 6 '14 at 16:25
  • @Stijn Yep! It indeed works locally, might be an IIS x IIS Express issue. – rla4 Mar 6 '14 at 17:40
  • 1
    @rla4 looks like the reason is Uri.AbsolutePath does not include query portion of the URL and # is considered query portion. Anyway, congrats on your shiny new diamond! – ShaWiz Mar 6 '14 at 18:35
  • Any chance this fix caused a new bug? – ShaWiz Mar 11 '14 at 13:53
  • @ShadowWizard It doesn't really look like, but it's possible :) We're looking at it right now. – rla4 Mar 11 '14 at 19:20
  • Cheers, glad to hear! :-) – ShaWiz Mar 11 '14 at 20:22

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .