29 lines
1.3 KiB
Plaintext
29 lines
1.3 KiB
Plaintext
HTTP/1.1 409 Conflict
|
|
Content-Type: text/html; charset=iso-8859-1
|
|
Cache-control: no-cache
|
|
Connection: close
|
|
Proxy-Connection: close
|
|
|
|
<html><head>
|
|
<title>I2P Warning: Destination key conflict</title>
|
|
<link rel="shortcut icon" href="http://proxy.i2p/themes/console/images/favicon.ico" />
|
|
<link href="http://proxy.i2p/themes/console/default/console.css" rel="stylesheet" type="text/css" />
|
|
</head>
|
|
<body>
|
|
<div class=logo>
|
|
<a href="http://127.0.0.1:7657/index.jsp" title="Router Console"><img src="http://proxy.i2p/themes/console/images/i2plogo.png" alt="I2P Router Console" border="0"/></a><hr>
|
|
<a href="http://127.0.0.1:7657/config.jsp">Configuration</a> <a href="http://127.0.0.1:7657/help.jsp">Help</a> <a href="http://127.0.0.1:7657/susidns/">Addressbook</a>
|
|
</div>
|
|
<div class=warning id=warning>
|
|
<h3>Warning: Destination Key Conflict</h3>
|
|
The addresshelper link you followed specifies a different destination key
|
|
than a host entry in your host database.
|
|
Someone could be trying to impersonate another eepsite,
|
|
or people have given two eepsites identical names.
|
|
<P/>
|
|
You can resolve the conflict by considering which key you trust,
|
|
and either discarding the addresshelper link,
|
|
discarding the host entry from your host database,
|
|
or naming one of them differently.
|
|
<P/>
|