Skip to main content

How can I navigate to a url programmatically with a correct referer header?



I have a flex application that uses the actionscript navigateToURL function to go to another system. However, a third party app that needs to be integrated checks for valid links by looking at the HTTP referer header, and it seems like that header is blank when using a navigateToURL call.





Is there a way in actionscript or javascript to programatically generate a url and go to it with a correct referer header?


Comments

  1. Aaah the referer header. I had a lot of frustration from this.

    Long story short, in Flex+AIR, no matter what you do (ex: manually change headers) the referer will ALWAYS be overwritten by the framework. I never actually tried it inside a browser (i.e. : not in AIR) so I can't confirm it behaves the same. You can try for yourself if you want by adding a new header to an URLRequest object like this :

    var request:URLRequest;
    request.requestHeaders.push(new URLRequestHeader("referer", "myReferer.com");


    Here's a bunch of interesting links confirming what I'm saying. I suggest you vote for the idea on Adobe Labs Ideas and comment on the bug on Adobe bugbase

    Post on Adobe Forums : HtmlLoader and "Referer" request header

    Adobe Labs Ideas : Don't set default referer in HTML Header

    Bug in Adobe bugbase : Default HTTP request referrer (referer header field) app://[app_name].swf causes denied access by some websites

    Question on the matter on SO : Intercepting network calls to force Html header referer to null

    ReplyDelete

Post a Comment

Popular posts from this blog

[韓日関係] 首相含む大幅な内閣改造の可能性…早ければ来月10日ごろ=韓国

div not scrolling properly with slimScroll plugin

I am using the slimScroll plugin for jQuery by Piotr Rochala Which is a great plugin for nice scrollbars on most browsers but I am stuck because I am using it for a chat box and whenever the user appends new text to the boxit does scroll using the .scrollTop() method however the plugin's scrollbar doesnt scroll with it and when the user wants to look though the chat history it will start scrolling from near the top. I have made a quick demo of my situation http://jsfiddle.net/DY9CT/2/ Does anyone know how to solve this problem?

Why does this javascript based printing cause Safari to refresh the page?

The page I am working on has a javascript function executed to print parts of the page. For some reason, printing in Safari, causes the window to somehow update. I say somehow, because it does not really refresh as in reload the page, but rather it starts the "rendering" of the page from start, i.e. scroll to top, flash animations start from 0, and so forth. The effect is reproduced by this fiddle: http://jsfiddle.net/fYmnB/ Clicking the print button and finishing or cancelling a print in Safari causes the screen to "go white" for a sec, which in my real website manifests itself as something "like" a reload. While running print button with, let's say, Firefox, just opens and closes the print dialogue without affecting the fiddle page in any way. Is there something with my way of calling the browsers print method that causes this, or how can it be explained - and preferably, avoided? P.S.: On my real site the same occurs with Chrome. In the ex