HTTP could not register URL inconsistency
Dani
2 wcf project on the same solution, app.config are the same (but for the
interface names)
1 project was created by the wizard, and the other one manually.
on the first project everything works fine. on the 2nd one I get this message:
HTTP could not register URL
http://+:8733/Design_Time_Addresses/MyProject/SubProject/myInterface/. Your
process does not have access rights to this namespace (see
http://go.microsoft.com/fwlink/?LinkId=70353 for details).
opening VS in admisitrator mode (it's a vista machine) make everything works
fine - but I don't want my server to run in administrative rights. it doesn't
need it, and it is less secured.
What am I missing ?
Dani
Arnold@arnold.com Mr. Arnold
"Dani" <Da...@discussions.microsoft.com> wrote in message
news:0A86BB2F-FF55-413C...@microsoft.com...
The second link is clearly telling you what you have to do to circumvent
the problem on Vista. And maybe, you'll need a generic user-id that can be
used for the Netsh command that is being used for Vista. You may also have
to look at the <impersonate> tag that can be implemented in a web or app
config file to impersonate a generic user.
Also, administrative rights on Vista don't have the same meaning like it
does on XP or previous versions of the NT based O/S, as Vista is a more
protected O/S than its predecessors,. even from someone or
something/program using admin rights. So, you may want to look at having
your solution using the Vista UAC Manifest to escalate privileges, which
only applies to the program's moment of escalation need. Also if this is a
.Net managed code solution, then .Net is looking at code intent and will
stop hostile code intent if something happens to inject itself into the
process, for what that is worth.
You don't look to be using IIS to host the WCF solution. And maybe you need
to think about hosting the solution with a Windows Service program harness
to host the solution. The Windows Service host for WCF solution could be
running under the Local/System account that has the need permissions or
some other account could be used.
<copied>
Configuring Namespace Reservations
Namespace reservation assigns the rights for a portion of the HTTP URL
namespace to a particular group of users. A reservation gives those users
the right to create services that listen on that portion of the namespace.
Reservations are URL prefixes, meaning that the reservation covers all
sub-paths of the reservation path. Namespace reservations permit two ways to
use wildcards. The HTTP Server API documentation describes the order of
resolution between namespace claims that involve wildcards.
A running application can create a similar request to add namespace
registrations. Registrations and reservations compete for portions of the
namespace. A reservation may have precedence over a registration according
to the order of resolution given in the order of resolution between
namespace claims that involve wildcards. In this case, the reservation
blocks the running application from receiving requests.
Running Windows XP or Server 2003
Use the httpcfg.exe set urlacl command to change namespace reservations. The
Windows Support Tools documentation explains the syntax for the Httpcfg.exe
tool. Modifying the reservation rights for a portion of the namespace
requires either administrative privileges or ownership of that portion of
the namespace. Initially, the entire HTTP namespace belongs to the local
administrator.
The following shows the syntax of the Httpcfg command with the set urlacl
option
Copy Code
httpcfg set urlacl /u {http://URL:Port/ | https://URL:Port/} /aACLThe /u
parameter is required when using set urlacl. It takes a string that contains
a fully-qualified URL that serves as the record key for the reservation
being made.
The /a parameter is also required when using set urlacl. It takes a string
that contains an Access Control List (ACL) in the form of a Security
Descriptor Definition Language (SDDL) string.
The following shows an example of using this command.
Copy Code
httpcfg.exe set urlacl /u http://myhost:8000/ /a
"O:AOG:DAD:(A;;RPWPCCDCLCSWRCWDWOGA;;;S-1-0-0)"Running Windows Vista
If you are running on Windows Vista, you can use the Netsh.exe tool instead.
The following shows an example of using this command.
Copy Code
netsh http add urlacl url=http://+:80/MyUri user=DOMAIN\user
Dani
I've found a utility that does it very easily.
My q. was why my wizard created server didn't need to register the URL.
once I learnd to look at netsh http show... I found that it was registered
(probably by the wizard) and that's why it worked and my own server didn't.
The App called HttpNamespaceManager and it is very nice...
Elevating the process is a bad option :-)
if you want to check it out.
Thanks again,
Dani
"Mr. Arnold" wrote:
> ..Net managed code solution, then .Net is looking at code intent and will