cancel
Showing results for 
Search instead for 
Did you mean: 

The network request is not supported in portal navigation

olaf_reiss
Participant
0 Kudos

Hello SDN,

we have established an internet connection for our SAP Enteprise Portal NW04 Stack09 via reverse proxy.

I can not see the navigation iviews e.g. in Content-Administration => Portal Content on the left side.

I have seen a lot of javascript in these iviews. We are routing the connection from the reverse proxy via two firewalls to the portal.

Has anyone an idea / experiences with this problem?

In addition the connection to my client is checked by a web sweeper which should not cause any problem because we are using ssl connection.

Thanks.

Best Regards,

Olaf Reiss

Message was edited by: Olaf Reiss

Message was edited by: Olaf Reiss

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi Olaf,

Were you able to resolve your issue with the network request is not supported error?

I am noticing the exact issue on EP 6.0 SP2 with IISProxy and FQDN being used.

If you have a solution could you please post it here.

many thanks!

Gaurav

olaf_reiss
Participant
0 Kudos

Hi,

what is FQDN?

Thanks.

Olaf Reiss

Former Member
0 Kudos

Hi Olaf,

When i wrote FQDN i meant the fully qualified DNS name of the website example: https://techtest.sap.com

We are not using the IP address to access the site.

thanks for your reply in advance.

Regards,

Gaurav

Former Member
0 Kudos

Olaf,

such errors usually occur if use IP address instead of what written in documentation (look at Installation Guide for EP):

http://<fully qualified portal machine name>:<HTTP port number>/irj

---

WBR, Lnk

olaf_reiss
Participant
0 Kudos

Hi Ivan,

we have replaced the ip by a fully qualified name, but the problem still exists. I do not work directly with the portal but via reverse proxy.

Best Regards,

Olaf Reiss

Former Member
0 Kudos

same kind of problem here

although we are in nw04 SP7.

we use a reverse proxy (iisproxy) for the sake of NTLM authentication.

we use FQDN only.

actually it is a bit different as we have JS errors on our DTN panel.

any ideas