|
That's not going to make a property in HttpContext null is it? In fact, if there was a missing using, it wouldn't even compile.
.45 ACP - because shooting twice is just silly
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001
|
|
|
|
|
I understand that you are calling from a Desktop application and it worked just fine for me. Can you provide additional informations to reproduce this? I believe you are using a SOAP web service. Here is what I did and which worked for me.
In Web service:
[WebMethod]
public string TestHttpContext()
{
if (HttpContext.Current != null)
return "Context is not null";
else
return "Context is null!";
}In Desktop application:
ServiceReference1.Service1SoapClient s = new ServiceReference1.Service1SoapClient();
string str = s.TestHttpContext();
Console.WriteLine(str); I also tried moving the HttpContext check to other class library as part of reproducing. But everything worked as expected.
If you can provide more information, I will try to reproduce.
Best wishes,
Navaneeth
|
|
|
|
|
Hi John
These two can give you the ip of a Client
string clientIP = Request.ServerVariables ["REMOTE_ADDR"];
or
string clientIP = Request.UserHostAddress;
Kind Regards
Vuyiswa Maseko
Vuyiswa Maseko,
Spoted in Daniweb-- Sorry to rant. I hate websites. They are just wierd. They don't behave like normal code.
C#/VB.NET/ASP.NET/SQL7/2000/2005/2008
http://www.vuyiswamaseko.com
vuyiswa@its.co.za
http://www.itsabacus.co.za/itsabacus/
|
|
|
|
|
This doesn't help when he is getting HttpContext.Current as NULL.
Best wishes,
Navaneeth
|
|
|
|
|
I believe you are blurring the lines between an Internet application and a desktop application.
When the application is running on the Internet you are executing on a hosting server which has a published IP address. Thus resolving it using HttpContext.Current.Request.UserHostAddress;
The IP address of a client machine executing a desktop application will be 127.0.0.1, the loop back IP address.
|
|
|
|
|
JimmyRopes wrote: I believe you are blurring the lines between an Internet application and a desktop application.
Look past the ego and actually read John's post.
John Simmons / outlaw programmer wrote: I created a web service
only two letters away from being an asset
|
|
|
|
|
Mark Nischalke wrote: JimmyRopes wrote:I believe you are blurring the lines between an Internet application and a desktop application.
Look past the ego and actually read John's post.
John Simmons / outlaw programmer wrote:I created a web service
He is either working with a web service or a desktop application. Never both.
Thus my comment about blurring the lines between Internet applications (web services) and desktop applications.
Please confine you snipping to my post and not try to make it a global war.
Better yet if you would like to continue to snipe take it to the soapbox.
modified on Sunday, October 18, 2009 5:19 PM
|
|
|
|
|
JimmyRopes wrote: He is either working with a web service or a desktop application.Never both.
Jimmy,
As per my understanding he is consuming a Web Service from a desktop Application. Current Context returning null because of that.
Abhijit Jana | Codeproject MVP
Web Site : abhijitjana.net
Don't forget to click "Good Answer" on the post(s) that helped you.
|
|
|
|
|
Right I was mistaken there.
When he calls from a browser there is a current context but not from a desktop application.
|
|
|
|
|
JimmyRopes wrote: When he calls from a browser there is a current context but not from a desktop application.
Exactly.
I am having doubt that regarding. It is not possible to get HttpContext from windows application as it is never running as an HTTP Context.
There may be some alternative solution.
Abhijit Jana | Codeproject MVP
Web Site : abhijitjana.net
Don't forget to click "Good Answer" on the post(s) that helped you.
|
|
|
|
|
Abhijit Jana wrote: It is not possible to get HttpContext from windows application as it is never running as an HTTP Context.
I would have to do some testing to see what is available from a desktop application. The debugger would probably be a good place to start.
Then when I found that I would need to see how to get it from a web service. I don't know if it is possible because there are real security concerns with accessing a client machine from the Internet.
An interesting question. If you have any thoughts please post them.
|
|
|
|
|
I would probably have to hit the web service via a http request so it could establish a context. But can't I somehow determine the IP address of the client without doing that?
Google hasn't been any help yet.
.45 ACP - because shooting twice is just silly
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001
|
|
|
|
|
John Simmons / outlaw programmer wrote: I would probably have to hit the web service via a http request so it could establish a context.
Do you access the web service from the client application with a HTTP connection? If so you are hitting the web service with an HTTP request.
John Simmons / outlaw programmer wrote: But can't I somehow determine the IP address of the client without doing that?
Probably because of the security restriction about accessing the client machine. Even just giving up the IP address would be a breach of protocol.
|
|
|
|
|
JimmyRopes wrote: Please confine you snipping to my post
I did. You were incorrect.
only two letters away from being an asset
|
|
|
|
|
Mark Nischalke wrote: Look past the ego
Maybe you don't think it is sniping but I find it offensive that you should refer to my ego and not just state where I was wrong, which I was and happened to admit it when I saw the error.
Take it to the soapbox if you want to post things like that.
|
|
|
|
|
Yet is was perfectly ok for you insult me.
JimmyRopes wrote: A look at your profile reveals that you are undoubtedly good at taking tests but that just means that you are good at taking tests, nothing more.
JimmyRopes wrote: Take it to the soapbox if you want to post things like that
Practice what you preach.
only two letters away from being an asset
|
|
|
|
|
Have fun talking with yourself.
|
|
|
|
|
JimmyRopes has posted a reply to your message at "ASP.NET":
You are a little man with a little intellect.
Impotent to say the least.
Simply Elegant Designs JimmyRopes Designs
Think inside the box! ProActive Secure Systems
I'm on-line therefore I am.
JimmyRopes
only two letters away from being an asset
|
|
|
|
|
JimmyRopes wrote: I believe you are blurring the lines between an Internet application and a desktop application.
No, I'm not confusing that.
Granted, during development, the web service is hosted on the local machine (which mine is). I full-well expect the IP address to be 127.0.0.1 in this case.
My *problem* is that using HttpContext.Current.blah_blah is evidently not the right way to retrieve the client IP address in a web service. The client in this case is a desktop application that happens to be running on the same box as the web service. I just want the web service to tell me the IP address it thinks the client is at. In the "real world", that IP would probably be a router/firewall that sits between the client machine and the internet.
Now, does it really sound like I'm confused?
.45 ACP - because shooting twice is just silly
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001
|
|
|
|
|
I realize now that you are not confusing that. My mistake.
I don't know if you will be able to retrieve the client machine IP address because of security concerns.
That is what makes it an interesting question for me.
John Simmons / outlaw programmer wrote: In the "real world", that IP would probably be a router/firewall that sits between the client machine and the internet.
Yes or a proxy server if one exists.
|
|
|
|
|
Sorry I misunderstood your question before that you are calling a web service from a desktop application.
Probably a good approach to take is to debug the desktop application and view some of the structures in a watch window. It is a hit or miss process so try a few different structures.
Maybe start out by assigning some things found in System to various objects. Intellisense [sp?] will tell you the object type when you select it. Assign it to a suitable object and put a watch on it.
Set a breakpoint after the assignments and you will then be able to expand the object and see what it contains.
As I mentioned it is more an art than a science, but after doing a few your instincts will develop and you will zero in on the promising structures.
Once you find out where the address resides the next problem will be to get it from the web service. I don't know if this is possible.
This is an interesting problem because it crosses the bounds between client machine and Internet application. There are serious security concerns about accessing the clients machine from the Internet.
Let us know if you figure out a way to do this.
|
|
|
|
|
JimmyRopes wrote: There are serious security concerns about accessing the clients machine from the Internet.
I am not trying to access the client machine. I simply want to determine its IP address at the server, and then return that address to the client.
.45 ACP - because shooting twice is just silly
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001
|
|
|
|
|
John Simmons / outlaw programmer wrote: I am not trying to access the client machine
Actually you are. You are trying to get the client machine to give up some information, the IP address.
|
|
|
|
|
It's not "giving up" anything. The originating IP address is part of every TCP/IP communication. If it wasn't, there would be no way to issue a response to a request.
.45 ACP - because shooting twice is just silly
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
