Popups not working in FireFox 3.5.*

[Former Member]

One of our applications in the SAP portal uses a web dynpro popup which is not working in FireFox 3.5.3 and 3.5.4

When we monitor the HTTP traffic we see a 404 when the popup is activated. There are no javascript errors but it is clear that firefox is misinterpreting a URL.

Our portal URL is portal.ourdomain.com

Our SAP URL is ext.ourdomain.com (where the Web DynPro apps reside)

In firefox we see

404 https://portal.ourdomain.com/irj/~ucfPOPUP_PAGE?sap-contextid=yyyyyyyyyyy&sap-wd-clientWindowId=0073...

In IE we see

200 https://ext.ourdomain.com/sap/bc/webdynpro/SAP/products/;sap-ext-sid=xxxxxxxxx--/~ucfPOPUP_PAGE?sap-...

IE is working correctly so it seems FireFox is misunderstanding the URL and fetching an SAP WebDynpro resource from the portal URL. The URL https://portal.ourdomain.com/irj/~ucfPOPUP does not exist so it fails.

Is this known behaviour and is there a fix?

We have SAP ECC 6.0 Basis Release 700 level 12

[floriangeorg_furtmller]

Hi all,

We have exactly the same issue after EHP1 upgrade on our systems... Marc did you found a solution for it, if yes how did you solved this issue? Any hints would be nice, thanks!

Regs. Florian

[Former Member]

@Florian, we had to change some of the framework javascript to work around the problem. This is only possible if you have a reverse HTTP proxy and can redirect content from the SAP server to a custom file server. The best solution is obviously to pathc or upgrade your Netweaver Application Server.

[Former Member]

Hi Marc,

SAP Note [1098009|https://service.sap.com/sap/support/notes/1098009] "Limitations for Web Dynpro ABAP" might be helpful for further analysis.

Best regards,

Andreas

[Former Member]

The problem is it works in FF as a standalone application but just when it's in the Portal we have problems.

[thomas_jung]

>

> The problem is it works in FF as a standalone application but just when it's in the Portal we have problems.

Perhaps that is part of the reason why FF 3.5 isn't supported yet on your release level. There are obviously problems as support for FF 2.0 doesn't even come until a later support package than what you are on.