User:MaxM

@timothy.high wildcard searches in the start of a search term are now supported in 10.0 but are disabled by default due to performance implications. Arne is going to document this setting soon and I'll update this thread once he does.

@guerric each item gets a server generated unique id upon addition. Any non-binary content bodies should be ok including json.

@crb from what I can tell, MindTouch has the same (inherited) behavior as mediawiki in the sense that the redirects are followed transparently. The URL on browser is the same as what you clicked by the content comes from the redirect target. Looks like thats still the current behavior in fact: http://www.mediawiki.org/wiki/User:Maxim11/myredirect I do agree that it is a little confusing. You do get a message saying that a redirect was followed but it may not be enough. As long as we still have a mechanism to allow users to modify the redirect, I don't see a reason to not use a 301 and have the real page URI reflect what your browser URI reports.

@crb from what I can tell, MindTouch has the same (inherited) behavior as mediawiki in the sense that the redirects are followed transparently. The URL on browser is the same as what you clicked by the content comes from the redirect target. Looks like thats still the current behavior in fact: http://www.mediawiki.org/wiki/User:Maxim11/myredirect I do agree that it is a little confusing. You do get a message saying that a redirect was followed but it may not be enough. As long as we still have a mechanism to modify the redirect, I currently don't see a reason to not use a 301 and have the real page URI reflect what your browser URI reports.

@crb, agreed -- the forwarding behavior can get some consideration as part of this spec. I think it's important to let a human user know one way or another that the link they clicked bounced them to another location. And the UI needs to allow a way to make changes to the redirect which means it has to know which redirect was followed. The location header in the 301 response can include a query parameter describing which link was clicked. Would that reduce the SEO benefits if the 301s leading to the definitive page had different values of a query param?

@crb, agreed -- the forwarding behavior can get some consideration as part of this spec. I think it's important let a human user know one way or another that the link they clicked bounced them to another location. And the UI needs to allow a way to make changes to the redirect which means it has to know which redirect was followed. The location header in the 301 response can include query parameters describing which link was clicked. Would that reduce the SEO benefits if the 301s leading to the definitive page had different values of query params?