0

Hi,

I used to monitor all eclipse related tags:

https://stackoverflow.com/questions/tagged?tagnames=eclipse~&sort=newest&pagesize=50

That generate (after a refresh) the full address:

https://stackoverflow.com/questions/tagged/eclipse+or+eclipse-plugin+or+eclipse-rcp+or+eclipse-cdt+or+eclipselink+or+eclipse-pde+or+eclipse-pdt+or+eclipse-3.4+or+eclipse-3.5+or+eclipse-plugin-dev+or+eclipse-wtp+or+eclipse-jdt+or+eclipse-3.6+or+eclipse-3.3+or+eclipse-3.2+or+eclipseme+or+eclipse-templates+or+eclipse-api+or+eclipse-3.5.1+or+eclipse-rap?sort=newest&pagesize=50

Two questions:

1/ I never notices the '+' (%2b). Before today there were only spaces (%20) between the tags and the 'or'

2/ this full address generates a HTTP Error 400. The request URL is invalid. (FireFox 3.6.8)
Do you know why?
Such addresses (even ones much longer) used to be served without issue before today.

Bonus question:

An address like:

https://stackoverflow.com/questions/tagged?tagnames=clearcase~%20or%20git&sort=newest&pagesize=50

generates the (working actually) full address:

https://stackoverflow.com/questions/tagged/clearcase+or+clearcase-remote-client+or+or+git?sort=newest&pagesize=50

Why the two 'or' between clearcase-remote and git tag?

0

See my answer here:
Why do I get an error 400 with one constructed URL and not with the other one?

And here:
Bug with single character tags in urls

Manually combining or and tag wildcards basically isn't supported at the moment, so use at your own risk. There are some boolean logic issues because we don't support parens to disambiguate.

0

Really, the UI needs to stop generating links to topics that lead to server errors. If I click a link and it 400's on a page that was not generated through any real trickery, there's something broken in the system. Look at the length of the generated url and prune it if it's too long, or send us to a "try a narrower search" page, or something.

You must log in to answer this question.

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