Webpage error details
User Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; .NET4.0C; .NET4.0E)
Timestamp: Wed, 23 Jan 2013 05:01:55 UTC
Message: Object expected
Line: 62
Char: 1
Code: 0
URI: http://localhost:4001/abc.aspx?id=12
I am getting this error in every page and specifically in ie8 . My script that is causing the issue is
<script type="text/javascript">DM_redirect("http://mobile.dudamobile.com/site/abc"); </script>
It works perfectly on both Google Chrome and Mozilla
How do i get rid of this issue
The Script being used is this
http://static.dudamobile.com/DM_redirect.js
I had a similar issue some weeks ago. You basically have to specify "javascript" in language because IE8 will read something else.
At last that worked for me.
Related
Im trying to achieve the follwoing -
While browsing to my nginx web-server with the following url - http://server/?device=10.10.21.102
I want proxy_pass=http://10.10.21.102 to be set and get the content of 10.10.21.102.
I've managed work it out with $arg_device but when destination page has images it breaks -
[09/Mar/2014:22:08:22 +0200] "GET /welcome.png HTTP/1.1" 500 594 "http://server/?device=10.10.21.102/" "Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; Trident/6.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET CLR 1.1.4322; InfoPath.3; Tablet PC 2.0; .NET4.0C)" "-"
When I access http://server/?device=10.10.21.102/welcome.png - I can see the image.
What would be the easiest way to solve this so css,js,images will be called as:
GET /?device=10.10.21.102/welcome.png
and not just
"GET /welcome.png
Thanks!
I've managed to solve this, with nginx_substitutions_filter module (http://wiki.nginx.org/HttpSubsModule)
It's very easily done.
When a user is visiting your site, is there a way of know what type of device they are using: computer, tablet, or mobile device? For example, when I get emails sometimes I see that it says sent via iphone; how do they know that? Any help or point me in the right direction would be very helpful.
Short answer: You can't.
Long answer:
All you have is the information in the HTTP User-Agent header, which usually contains the OS name and version.
Usually, browsers running on Mac OS and Linux send enough information to identify the exact OS. For example, here's my User-Agent header:
Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.0.7) Gecko/2009030423 Ubuntu/8.10 (intrepid) Firefox/3.0.7
You can see that I'm running Ubuntu 8.10 Intrepid Ibex.
And here's what Firefox and Safari 4 Beta report on my MacBook Pro:
Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.0.7) Gecko/2009021906 Firefox/3.0.7
Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_5_6; en-us) AppleWebKit/528.16 (KHTML, like Gecko) Version/4.0 Safari/528.16
Windows browsers, on the other hand, usually only report the OS version and not the specific package (Pro, Business, etc.):
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:x.x.x) Gecko/20041107 Firefox/x.x
I did not write this awnser i copied it from: Detect exact OS version from browser Thanks to: Can Berk Güder
I'm working on some logging functionality for a website, and I need to update a table with information about the users' browser info. The table was created a while ago by someone else, and I have no idea where they were getting this info. Does anyone recognize this? (each line is a single row)
Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; GTB0.0; .NET CLR 1.1.4322; InfoPath.1; .NET CLR 2.0.50727)
Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0; FunWebProducts; FBSMTWB; SIMBAR={8FCFDD51-4B26-489E-A39E-AB2744B
Java/1.6.0_06
Opera/9.80 (Windows NT 5.1; U; en) Presto/2.5.24 Version/10.53
BlackBerry9630/4.7.1.61 Profile/MIDP-2.0 Configuration/CLDC-1.1 VendorID/105
It's in the HTTP User-Agent header.
Here is the code you would use in ASP.
Dim sAgent: sAgent = Request.ServerVariables("HTTP_USER_AGENT")
For face book and Google Plus I am getting 407 and 403 result code. I used the below URL for generating face book share and Google plus icon
http://www.google.com/webmasters/+1/button/
http://developers.facebook.com/docs/reference/plugins/like/
Can someone suggest me what I am missing
Webpage error details
User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET4.0C; .NET4.0E; InfoPath.3)
Timestamp: Thu, 12 Jan 2012 18:20:17 UTC
Message: Object doesn't support this property or method
Line: 4
Char: 1
Code: 0
URI: https://connect.facebook.net/en_US/all.js#xfbml=1
Message: Permission denied
Line: 1
Char: 8164
Code: 0
URI: https://platform.twitter.com/widgets/tweet_button.1324331373.html
The page you are Liking or plus 1'ing probably is not accessible to the linters being used (meaning it is not a public URL). For facebook you can quickly determine the status of your URL by linting it at: https://developers.facebook.com/tools/lint
I have confirmed that my Control Adapters are not triggering in Chrome and Safari. I've debugged, and the breakpoints inside the adapters just don't get hit in Chrome/Safari, when they work perfectly find in Firefox/IE. So, for Chrome/Safari, IIS is just ignoring the mapping.
My AdapterMappings.browser file looks like this:
<browsers>
<browser refID="Default">
<controlAdapters>
[...adapters here....]
</controlAdapters>
</browser>
</browsers>
This should provide mappings for all browsers, correct?
I used the Charles proxy to check what user agents were being sent. They are:
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US) AppleWebKit/532.5 (KHTML, like Gecko) Chrome/4.1.249.1064 Safari/532.5
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US) AppleWebKit/531.22.7 (KHTML, like Gecko) Version/4.0.5 Safari/531.22.7
Any idea why this would be? Everything I've read tells me that my browser mappings are correct? And, as I said this works for IE/Firefox, so I know my configuration is technically correct.
We found the problem. It was errant code that specifically disabling the adapters in Chrome/Safari. They work fine, normally.