Beefy Boxes and Bandwidth Generously Provided by pair Networks
Perl-Sensitive Sunglasses

Re: Redirect Script unless called from previous script

by cLive ;-) (Prior)
on Nov 02, 2012 at 16:41 UTC ( #1002008=note: print w/replies, xml ) Need Help??

in reply to Redirect Script unless called from previous script

Simple, works for general case (but fakable) - check HTTP_REFERER environment variable.

More complex, works for all - have script A send a signed request, and have script B only run if that request is valid. There are many ways to do this - the best will depend on the environment you're coding in. Eg, Mojolicious has built in signed cookies, for example.

  • Comment on Re: Redirect Script unless called from previous script

Replies are listed 'Best First'.
Re^2: Redirect Script unless called from previous script
by Anonymous Monk on Nov 02, 2012 at 16:46 UTC
    I guess a better way of saying what I'm looking for is a 'conditional redirect'. I already have it looking at the HTTP_REFERER, so it will only run from my domain. However, I want it to only run from a specific script on my site, and if run without that script, I want it to redirect to an error page.

      The other Anonymous Monk and cLive;-) already gave you the answer, but didn't tell you how to implement it. An easy (though not entirely foolproof) way to do it is have each script that is allowed to call it pass an additional "password" parameter. The restricted script then receives that input and checks that it's valid before proceeding. It's reasonably secure because it's getting passed within your server, and the user will never see the required parameter list to make the restricted script work.

      Someone could, in principle brute force it, but if you pick a long random string the time required is long. It's probably essentially the same code you're already using with the HTTP_REFERER, but with a different parameter, and the calling scripts have to send it explicitly. There are various ways to make the brute force attack less economical by increasing the time required per call by a small amount- any single call will barely notice, but it adds up when you're doing a lot of them.

      There may also be some complicated way you can do it by setting permissions so that your www user (or whatever your server runs as) isn't allowed to call it, but then the scripts that can call it can sudo to be a user with the correct permissions. This seems like a sketchier approach to me, since it probably uses system calls and may expose you to other security risks in less predictable ways.

      EDIT: Your Mother's approach is better than either of the above.

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://1002008]
and all is quiet...

How do I use this? | Other CB clients
Other Users?
Others meditating upon the Monastery: (5)
As of 2017-08-22 11:53 GMT
Find Nodes?
    Voting Booth?
    Who is your favorite scientist and why?

    Results (335 votes). Check out past polls.