Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

I am using firefox to access SAP based application. Getting error: Sorry, your browser/program is not supported by Web Dynpro! "

  • 4 replies
  • 523 have this problem
  • 1 view
  • Last reply by DIV1

more options

HRMS is based on SAP. We access application using web browser. It was working good in firefox version 3.6. But after upgrading it to 4 RC. it is giving message as: "Sorry, your browser/program is not supported by Web Dynpro!"

URL will not be accessible as it is intranet based application.

HRMS is based on SAP. We access application using web browser. It was working good in firefox version 3.6. But after upgrading it to 4 RC. it is giving message as: "Sorry, your browser/program is not supported by Web Dynpro!" URL will not be accessible as it is intranet based application.

All Replies (4)

more options

The problem lies in the CVS branche notice of the useragent.

This was solved using an option called: general.useragent.override

To add this: http://support.mozilla.com/en-US/questions/750405

Big difference between me and the useragent listed in the solution is that I first looked up my useragent string on UserAgentString.com. The only changes I made was this:

Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:1.9) Gecko/20100722 Firefox/3.6.15

I have change rv:2.0 --> rv:1.9 and Firefox/4 --> Firefox/3.6.15

This worked for me.

more options

Thank you Martva it worked perfectly.

more options

Playing with the user agent string does seem to get me past the "Sorry" error message, but I find that other aspects of my company's SAP portal are still broken. For example, drop down menus in our portal do not actually drop down. Also, refreshing our Universal Worklist does not seem to work either.

I'd say this is still an open issue that Firefox and SAP need to resolve.

more options

Martva's proposal is not really a "solution". Rather, it is a "workaround".
If the browser is technically capable of rendering the site/page, but the creator doesn't allow access, then the solution is for the originator (SAP / Web Dynpro) to fix their bugs.
If the browser is not technically capable of rendering the site/page, because the creator has not produced a standards-compliant product, then the solution is for the originator (SAP / Web Dynpro) to fix their bugs.   (Or, rarely, it could be that the standards should be updated to support important features that were lacking.)


See these resources:
"The real pitfall here is that browser masquerading doesn't fix the underlying problem: badly configured, inflexible Web servers. Masking your browser may be necessary for you to use the site, but it doesn't give the site owners any incentive to fix the site. "
http://www.ericgiguere.com/articles/masquerading-your-browser.html

"Spoofing the UA is essentially lying to others about what you are using. [....] Additionally, if you find a website that does not render properly in SeaMonkey, read the Mozilla technology evangelism page to find out what you can do. SeaMonkey is built to comply to W3C standards; so when a page does not render properly, it is almost always the fault of a webmaster, [...]. "
http://seamonkey.ilias.ca/browserfaq/UAspoofing

Modified by DIV1