I would like to create a page, that displays the skype status of logged user like this:
http://www.skype.com/intl/en-us/tell-a-friend/get-a-skype-button/
It works fine on HTTP, but I have to use https protocol.
MyStatus link is a http link that displays the status of user, but browsers do not display this correctly or display a notification because of http link.
Has anyone had experience with this? Any suggestions?
UPDATE
The solution is you have to create a proxy handler (ashx) file, that catches the webrequest and returns the same content in response.
Can't you just get the data yourself and then display whatever you want that indicates their status.
http://mystatus.skype.com/user.xml
You need to use this specific secured (HTTPS) domain for Skype widgets:
https://secure.skypeassets.com/i/scom/js/skype-uri.js
Related
In my MVC application, I have used Ajax's Response.StatusText to display custom error messages to user whenever there is some error.It works fine but when I deploy my application on AWS, the StatusText gets removed and only the code is displayed. Got to know that because of using HTTP/2, the statusText gets removed.
Is there a way to show custom error message in Ajax error over HTTP/2 ?
Thanks in advance.
I don't think the HTTP Status is the best place to put these. You should either put this status in the body, or possibly in a custom HTTP header.
I tried to send sms via the HTML API and I would like to use the callback function, but clickatell doesn't call the entered URL.
I could send via this URL and I recived the sms https://platform.clickatell.com/messages/http/send?apiKey=_API_KEY_&to=_PHONE_NUMBER_&content=Test+message+text&callback=1
SMS Integration \ Settings \ Enable delivery notifications is enabled and I entered the url in this format: http://domain.co.uk/sms/status. I tried the POST and GET method too.
When I enter this url to the address bar than this is works fine.
I read the documentation and I found the question from 2015 on stackoverflow, but this is a new API, I didn't found any other settings for callback url. I tired the parameter named callback with multiple value, but this didn't worked.
When I didn't found more settings I activated this integration, but I didn't found any difference.
Have somebody any idea?
I am trying to post to a server listening on a different port, but FireFox insists on sending an OPTIONS request because apparently I am not using the proper URL. How can I POST to localhost:8161 without FireFox thinking the request might be cross domain and sending OPTIONS?
Here you have an answer:
How do I send a cross-domain POST request via JavaScript?
It is not easy to detail it in a better way.
You can add iframe whose src contains url with different port
As the title may possibly suggest, I'm wondering what's more secure for AJAX requests: POST or GET. I can't work out which is better because they're both hidden from the user due to the URI being sent via. AJAX, not in the URL bar.
Thanks,
James
Neither add any security against either man-in-the-middle attacks or the end user. Both can be intercepted and tampered with using Wireshark, Firebug, or other tools.
If you want security against interception, you can use HTTPS. That does not prevent the user from sending requests manually, though.
It's almost trivially easy to inspect the contents of both post and get values. Your best bet, if you do not want the user to be able to get at that data directly, is to encrypt it, and / or send it over ssl.
There are no security differences between POST and GET used in AJAX. They are not hidden from the user - a simple tool like Fiddler would allow the user to see those requests. the payload in both is in plain text (ie, as your script created it). The only difference is that POST payload is in the body of the request and GET payload is in the query params of the URL.
They are not hidden from the user at all; install FireBug on FireFox and they are able to see the URI. Your choice of using GET and POST depends on the data sent; and if you going by REST standards, depending on the operation.
Treat an AJAX call as you would with information coming from the client through a form and through the address bar : Verify and sanctify.
They can view the page source and see where your target URL is and what parameters are being passed either way.
Would there be any problems calling an HTTPS page (e.g. a credit card authorisation service i.e. WorldPay) from a standard HTTP page via AJAX?
I can't imagine why there would be a problem, the response would be an HTML page which I could then embed in a result pane or such like?
Yes this would be a Cross domain posting and would be blocked by the browser.
Anthony is right, but what you could do is create a local page the AJAX calls and that communicates with the HTTPS service via cURL or something else and returns. That way everything is done locally according to Java script.