X
Tap here to go to the mobile version of the site.

Support Forum

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

Posted

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.

Additional System Details

Sites Affected

http://

Installed Plug-ins

  • This plugin allows the user to quickly add people from the BluePages website to their Lotus Notes address book.
  • Google Talk Plugin Video Accelerator version:0.1.43.5
  • Version 1.9.2.0
  • Yahoo! activeX Plug-in Bridge
  • Office Plugin for Netscape Navigator
  • DivX Web Player version 1.5.0.52
  • npdivxplayerplugin
  • IBM GLOBAL PRINT PLUGIN VER 4.1
  • NPRuntime Script Plug-in Library for Java(TM) Deploy
  • Adobe PDF Plug-In For Firefox and Netscape 10.0.1
  • Google Update
  • BrowserPlus -- Improve your browser! -- http://browserplus.yahoo.com/
  • Shockwave Flash 10.2 r152
  • Adobe Shockwave for Director Netscape plug-in, version 11.5.9.615
  • Java Plug-in 1.5.0 for Netscape Navigator (DLL Helper)
  • WebSphere Client Java Plug-in
  • Next Generation Java Plug-in 1.6.0 for Mozilla browsers
  • Next Generation Java Plug-in 1.6.0_23 for Mozilla browsers
  • Windows Presentation Foundation (WPF) plug-in for Mozilla browsers
  • 6.0.12.46
  • RealPlayer(tm) LiveConnect-Enabled Plug-In
  • Version 1.1.7, copyright 1996-2011 The VideoLAN Teamhttp://www.videolan.org/
  • Npdsplay dll
  • DRM Store Netscape Plugin
  • DRM Netscape Network Object

Application

  • User Agent: Mozilla/5.0 (Windows NT 5.1; rv:2.0) Gecko/20100101 Firefox/4.0

More Information

Sorry, your browser/program is not supported by Web Dynpro!

martva 0 solutions 1 answers

Helpful Reply

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.

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.

Question owner

Thank you Martva it worked perfectly.

Thank you Martva it worked perfectly.
bamclark 0 solutions 1 answers

Helpful Reply

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.

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.
DIV1 0 solutions 2 answers

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

Martva's proposal is not really a "''solution''". Rather, it is a "''workaround''". <br> If the browser <u>is</u> 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''. <br> If the browser <u>is not</u> 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''. &nbsp; <small>(Or, ''rarely'', it could be that the standards should be updated to support important features that were lacking.)</small> See these resources:<br> '''"'''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. '''"'''<br> [http://www.ericgiguere.com/articles/masquerading-your-browser.html 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, [...]. '''"'''<br> [http://seamonkey.ilias.ca/browserfaq/UAspoofing http://seamonkey.ilias.ca/browserfaq/UAspoofing]

Modified by DIV1