How to Secure my jquery ajax call more secure ?

Question

3.67/5 (2 votes)

See more:

I am using Jquery.ajax call in from client side to wcf its working fine but am giving the whole url of the wcf service in ajax call . if anyone see the page source they can easily come to know about where my wcf rest service is located. how can i protect ?

Posted 30-Dec-13 1:23am

LENINRAJ RAJENDRAN

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Sandip.Nascar · Accepted Answer · 2013-12-30T01:36:00

Same way you protect a web request call, you can follow the same while making an ajax call.

Your ajax call is hitting a wcf and you want to hide the wcf url.
But only by hiding will not solve your purpose.

Like I can easily track the url from the page you are calling even if there is no ajax call.
So, it's just few seconds effort to track the url.

The best way to handle such situation is to authenticate the wcf by sending login credential.

Another nice approach which I prefer is to call a aspx handler from ajax and write your wcf call within the handler. Ensure you authenticate through session that the handler is called from within the application. Just to ensure the handler is not called externally. If called externally, do the audit trail recording the ip address of the user and kick the user to the login page.

Both the approach will work for sure.

Good luck!
Cheers