Can anyone tell me how can i get "vastresponse.xml" file from Openx server? What is the request url we have to send if we need "vastresponse.xml" of particular ad.I want to use this in jwplayer.
Related
i have a real-time database in firebase and i want to send an http request using PUTTY,
but i need to put in PUTTY some host name(or ip address) but i cant understand what is firebase hostname..
i tried google.firebase.com and it doesnt work,and i tried my url database and it doesnt work..
when i send a get request using POSTMAN or curl to my database it works properly
can you tell me how to know the host-name of google firebase? or maybe tell me how to send proper get request? becuase maybe this is the problem(i want to send get request using PUTTY)
I am setting up Fortumo Web SDK payment for my website,
I am putting the url in "To which URL will your payment requests be forwarded to?"
I am using some DB related code here so that it would insert the code in DB and I could check it afterwards,
But when I test the payment it doesn't touch the GET URL and didn't send any request to this URL.
Need Support,
thanks
Finally, I am able to solve the issue, actually the main problem is that fortumo Web SDK works only with HTTPS links and send payment response as a GET Request to the specified link at fortumo configuration.
so no my link starts with https://multanwebtech.com/.......php
I have an application that allows users to upload contents to Amazon S3, and returns the link of the uploaded content.
I have been wondering how to allow only users that own the content to access it, and i got into http://docs.aws.amazon.com/AmazonS3/latest/API/sigv4-auth-using-authorization-header.html the authorization header.
A way to use it i thought is: generating a link to my application host for each content (e.g: from bucket.s3.amazonaws.com/29347524.jpg to -> myapp.com/image/154155.jpg) and serve it to user. When i receive a request i'll be checking if the user is authenticated in my application or not, and in successful match i'll allegate the authorization header to the request and forward it to amazon.
I would like not to download the content from amazon's server from my application's server and serve the content to the client. I think this is a useless waste of band.
Is there maybe any way to forward the request after adding some headers? So that the client is answered by Amazon when he requests the content but the request is made to my server and modified in some parts.
Do you know any other way to perform an authentication like this on Amazon's S3 content ? Any suggestion will be appreciated
I would look at the pre-signing facility in S3: http://docs.aws.amazon.com/AmazonS3/latest/API/sigv4-query-string-auth.html
Your application server can generate a time-bound URL as described there, and redirect the user using HTTP 302 with the corresponding Location header.
If you Google for "amazon s3 presign url", you'll find a few more resources: both blog posts and official Amazon docs.
When I create an API proxy in Apigee (my account is new), and then paste that newly created url into my browser, I get an unexpected result.
The data returns as I would expect from my underlying API on my system. But, the URL in the Browser changes from the Apigee URL to my original URL.
I don't really even want the user to know that my underlying URL exists. We are planning on putting Client Side SSL in place so that only the Apigee system can talk to our underlying API, but this is still behavior that I wasn't expecting.
Any help or guidance would be most appreciated.
The only way that you would see your targets url in your browser is if your target is returning a 302 redirect with said url in the response. This often happens if in apigee your pointing to a http target with a rewrite rule that auto redirects to an https address.
The best way to fix this would be to change your target to an https address so the redirect does not happen.
If it is some other reason you should look at the trace tool to see exactly what traffic is going through apigee, this can give you a good perspective on what changes on the request as it goes through the platform.
I want to understand the technical background why it is not possible to track an HTTPS website with Piwik, when Piwik itself is installed on an HTTP server?
Somebody said, that if you would do that the browser would come up with an error message, but why?
I mean you do an HTTPS request, and on the bottom of the site is the tracking code to the HTTP Piwik site, that gets requested immediately. What's wrong about that?
All resources (such as the requests to Piwik) of the site requested through HTTPS have to go through the very same protocol since, otherwise, you will receive varying warning messages from different browsers (along the lines of "Your connection to XYZ is encrypted, however it contains resources that are not secure [...]").
So, to alleviate the problem, also Piwik has to be available via SSL.
The Piwik Javascript snipped already checks the protocol and redirects the user to the respective protocol. Now all you need to ensure is that your Piwik installation resides somewhere that has a valid SSL certificate.