Jump to content

Recommended Posts

Just double checking:

 

I have a <script> that calls a php file to compose the javascript. Just double checking: when a browser loads content from a <link> or <script> tag, it always sends the appropriate HTTP_USER_AGENT string as well, correct?

 

I just want to sure it ALWAYS sends it before i rely on its functionality.

 

Thanks

Every HTTP request that the browser makes includes the HTTP_USER_AGENT as part of that request. External css and external javascript files are requested by the browser using a HTTP request.

 

ohh ok makes sense. Thanks! Also, one more question:

 

I'm using this <script> call to log info about a business. How can i validate it? A.K.A., i have this url (http://mysite.com/log?id=6).. Obvisouly, I don't want someone to be able to log go directly to that URL and intentionally try to screw with results. So... is the only way to do this is to use a session() to limit data logged per user. BUT, then "bad-people" could just delete their cookies, change their IP, and continue to process.

 

Any solutions to this? There's gotta be something! (especially seeing as though there's tons of JavaScript API"s by facebook/group/big guys)

Thanks!

 

EDIT: Also, i know there's JS to be used to pass the current URL in the url to the javascript... but that could be forged as well, i assume

This thread is more than a year old. Please don't revive it unless you have something important to add.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.