Loading...
 
Skip to main content

Features / Usability


404 Error when Linking Out

When posting external links on wikipages, I get a "do not have permission" error. They can be wikiscript or HTML, same error.

I've been trying to figure out what I missed - everything looks like I can do so, but I'm basically clueless, so it's probably something easy.

If someone would be good enough... What are all the things I must have on / off to do so?

I'm a co-admin at Levi's site. To add some additional information, whenever there's an external link posted in any wiki page on the site, when clicking the "save" or "preview" buttons it immediately errors out. The error that comes up is:

Forbidden

You don't have permission to access /tiki-editpage.php on this server.

Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.


The exception seems to be in the forums. We can link out from the forums to our heart's delight. It's just that any time an external link appears anywhere else, it gets canned and we're not sure why. It can be wiki code, HTML, or even a web page that's been parsed by autolink.

I did a Google search, and found where someone posted that he'd discovered it was an overzealous security setting, but he didn't post exactly what the setting was.

Thanks!

Chris


Ok, to followup:

Some experimenting has shown that when I type a link thusly:

[//www.google.com]

it actually creates the link, but displays it thusly:

//www.google.com

while linkifying it properly, but with no "external link" icon. But if I type it in as follows:

[http://www.google.com]

it dies.

Further experimentation shows:

[://www.google.com|testing]

generates the link, with the "external link" icon, but appending the ://www.google.com text to the site URL. In other words, not linked correctly.

Curiouser and curiouser.

The links must be fully qualified, or else they are assumed to be relative to your domain.

[www.google.com] = www.google.com (no http:// prefix, assumed to be a relative link)
[http://www.google.com] = http://www.google.comQuestion
[http://www.google.com|Google] = GoogleQuestion

Tiki will also attempt convert some text strings to links (even without the [foo] syntax.:
www.google.com = www.google.comQuestion
http://www.google.com = http://www.google.comQuestion

Please see the docsQuestion for details.

HTH,

-RickQuestion
Need more help? Try TikiWiki for Dummies SmartiesQuestion or read my Tiki Blog or visit my UserPage

Hi Rick, thanks for your response.

When I type

[http://www.google.com]

I get the error.

In fact, when the characters

http://

appear in sequence, I get the error. It doesn't matter what the link is to. It doesn't matter whether or not it appears in [ ]. I can even enclose it in and it still does it. Believe me, we've tested it exhaustively.

Aitch tee tee pee colon slash slash gives me an error.

>I'm not sure then... what Tiki version are you using?

According to General Preferences, it's Tikiwiki 2.0

Chris


Ok, further experimentation tells me that it seems to be related to the "http://" combination of characters. But not in the forums, just everywhere else.

Hi,

I have exactly the same problem, and indeed it is just the 'http://' combination of characters. Interestingly, I also experienced this with MediaWiki.

Has anyone found any new information on this problem?

David

Just to follow this up, I informed my hosting provider about the external links being stopped in both TikiWiki and MediaWiki. They changed some security settings I did not have access to, and it works a treat now.

So, if you are having the problem of submitting the characters 'http://' in your wiki edits, it is a problem with your server set up. Contact your host.

David


These errors about not having permission are indeed a server setup issue. This is related to a setting called mod_security. You need full access to the server configuration to be able to change this, generally using SSH. If you are on a shared hosting environment, where you share a machine with other sites, you will not have access to set this variable, and will need to ask your hosting provider to do it for you. Make sure you are very specific with your problem and the file or procedure that is causing it, and most providers will respond quickly, it is something they are very familiar with. It happens quite often.