Error 310 (net::ERR_TOO_MANY_REDIRECTS): There were too many redirects.

[InformationNirvana]

I just created an article.
A site I use doesn't have the full VaultWiki.
I posted a new article.
It has a quote from the forum, a quick blurb, and a YouTube video.

I can't view the article because it says this:
Error 310 (net::ERR_TOO_MANY_REDIRECTS): There were too many redirects.

[pegasus]

If you are using VaultWiki Lite, you can't rewrite the wiki URLs to something like site/wiki/article. It will cause an infinite redirect.

If this isn't the cause, it might depend on the title that is used, the forum's language setting, or the fact that VaultWiki Lite doesn't support UTF-8.

[aebn]

how does one determine if it the language, or encoding or what? what settings are we talking about and what should they be?

[pegasus]

Unless you're a developer, you should just report the aforementioned values to us. It's not that they should be anything in particular, but some setting values might have issues we haven't seen yet. Some might be quite obscure and trying to find the cause on your own could be very frustrating.

By "language setting", I mean the forum's Language Chooser (usually in the footer). Did you change the value from one language to another while on a wiki page? Also what language is the wiki page, and is it different from the chooser state?

[aebn]

turns out vaultwiki doesnt appear to handle redirects unless you are lkistening on port 80.
my instance was listening on 81,after changiing to 80, all good.

assuming nonstandard HTTPS port would probably failas well

[pegasus]

If you're running vBulletin >= 4.0.3, then there should not be an issue, because it has a very reliable way of reporting the requested URL. In vBulletin < 4.0.3, the methodology is flawed and our code is convoluted to correct some issues, and doesn't appear to include ports.

In versions above and including vB 4.0.3, when canonizing the URL of an article, VaultWiki doesn't force any particular port, unless you have specified that port as part of the wiki base URL setting. If the port in the setting is incorrect (or missing), and the server is listening on a different (or not-80) port, then it's possible this would cause redirect issues in VaultWiki if the server performs an internal redirect to port 81, or listens on it and then sets PHP's SERVER_PORT value to 80 before handing off the request.

VaultWiki takes the current URL from vBulletin, and vBulletin only understands ports 80 and 443 as acceptable unmentioned ports. Because of this, any custom port value would have to be included in the base URL setting, or the server's listening port would have to be changed to one of them.