Re: Client Information

You missed my purpose.
I am not trying to use this information to identify proper usage. Just
simply collecting data of who is using it and when. If the IP address is
that of a NAT box or some other piece of hardware that is fine. The people
that have asked me to get this information realize everything that you have
mentioned and they realize that this information may not always be accurate
or available. That, however, doe snot stop them from wanting to log it.
For arguments sake, lets say the information I am trying to retrieve is
available due to however the client has set up their site. I have managed
to get the IP address but I am still stuck on how I can get the URL. So far
I have only been able to retrieve the address of the ASMX file not whatever
called it.
If you are unable/unwilling to help or if this just simply is not
possible please simply just say so. A lecture on networking and/or coding
may be useful to some, and I'm not saying I don't appreciate your insight,
it does not help me get the info I need or convince the bosses that they
don't want it.


"John Saunders [MVP]" <john.saunders at trizetto.com> wrote in message
news:uFM18ulIIHA.2480@xxxxxxxxxxxxxxxxxxxxxxx
"Scott" <Scott@xxxxxxxxxxxxxx> wrote in message
news:uPW36QkIIHA.1316@xxxxxxxxxxxxxxxxxxxxxxx
Ok, in detail...
I have created a WebService in VS 2005 using C# that returns the
results
of a database search in an XML dataset .
The purpose is to allow clients access to this webservice so that
they
can utilize the search options I make public through the webservice. By
doing it this way clients who use this service should be able to
incorporate
my data into their website as if it were their own.
What I am trying to record is the URL of the page that accessed the
webservice and the IP of the domain that page is under.
For example:
The company XYZ.com (IP: 111.111.111.111) would like to use my
data
on their website. using the webservice I have created they access the
webservice through code on www.xyz.com/search.aspx which returns an XML
dataset which they can display on their page.
In this example what I would like to record is
"www.xyz.com/search.aspx"
and "111.111.111.111".

Let me know if that still doesn't make sense.

It makes sense; it's just not practical.

As another poster as indicated, you can get the IP address that accessed
the
service. This may or may not correspond to an actual web server. It could
just as easily be the IP address of a NAT box or some other piece of
network
equipment.

Picture the classic seven-layer model. IP addresses belong to the Network
layer. This means that the Network layer can do whatever it wants to with
an
IP address, as long as it doesn't screw up the Transport layer. In other
words, your code (in the Application Layer) shouldn't be depending on IP
addresses to mean anything at the Application Layer. They are Network
Layer
artifacts.

If you want an identifier you can depend on at the Application Layer, you
will need to create one: a certificate, for instance.

You will never get the URL of the page that called the service because
pages
don't call services - code does. That code may or may not be on a web
page,
and it may or may not know the URL of the web page. That URL might or
might
not be useful in locating the page again from a browser's address bar, but
it's not likely to be too useful to use as an identification - consider
the
case of a web farm, for instance, or the case where the URL of the page
has
nothing to do with the domain of the company (assuming that the company
only
owns a single domain).

You go on to mention the IP address of the domain. That term has no
meaning.
Domains do not have IP addresses, per se.

All in all, you should just totally forget the idea of the networking
infrastructure doing your job for you. If you need to identify users
and/or
the company they work for (or some other licensed entity), then you need
to
do that explicitly, with your own code, written to your own requirements,
and not written to the requirements of IP Networking, or of Web Browsing,
or
of DNS Domains.
--
--------------------------------------------------------------------------
------
John Saunders | MVP - Windows Server System - Connected System Developer




.

Relevant Pages

  • Re: Client Information
    ... of a database search in an XML dataset. ... The purpose is to allow clients access to this webservice so that they ... IP addresses belong to the Network ... This means that the Network layer can do whatever it wants to with an ...
    (microsoft.public.dotnet.framework.webservices)
  • Re: [9fans] Do we have a catalog of 9P servers?
    ... network layer data units, ergo, NAT again. ... The "packet ...
    (comp.os.plan9)
  • Re: Need a script to understand names posts
    ... the physical layer of the ISO model, augmented by providing all of the logic ... a network model that does more than just detect the fact that packets ... and brings them back onto the network as if they had never been lost. ... the packets previously lost will never ever be lost again, ...
    (microsoft.public.scripting.wsh)
  • Re: Machine learning
    ... They usually consist of neurons, ... input layer, the intermediate layer and the output layer. ... into the network using a method called "back-propagation". ... Train the network until it recognises characters reliably.. ...
    (borland.public.delphi.thirdpartytools.general)
  • RE: Logged WSE 2.0 error: WSE350
    ... I too found this message thread, but the supposed cause (a network package ... So the corruption could occur anywhere on the ... As for the webservice application, is it newly deployed or has been running ... Microsoft MSDN Online Support Lead ...
    (microsoft.public.dotnet.framework.webservices.enhancements)