It's all about the answers!

Ask a question

DNG OSLC selector url in Iframe is going into an infinite flickering loop


Jayakumar P (11) | asked Jun 30, 9:18 a.m.

 We need to integrate DNG links into an external application. We have embedded the selector url for Requirements in an Iframe of the external application. The selector URL works when we are running both DNG and external application in the same server. However when the external application runs in a different host the selector delegated UI goes into an infinite flickering loop of page loads. I noticed that in case of running the applications(DNG and the external app) in same host, the JSESSIONID is getting passed in the request header and header "Sec-Fetch-Site: same-site" is set. When the hosts are different JSESSIONID is not getting passed and header "Sec-Fetch-Site: cross-site" is set.


How can we resolve this issue? Appreciate any help.

Headers when running in different host
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,image/apng,/;q=0.8,application/signed-exchange;v=b3;q=0.9
Accept-Encoding: gzip, deflate, br
Accept-Language: en-US,en;q=0.9
Connection: keep-alive
Host: xxxxxx4520:9443
Referer: https://xxxxxx8055/
sec-ch-ua: " Not;A Brand";v="99", "Google Chrome";v="91", "Chromium";v="91"
sec-ch-ua-mobile: ?0
Sec-Fetch-Dest: iframe
Sec-Fetch-Mode: navigate
Sec-Fetch-Site: cross-site
Sec-Fetch-User: ?1
Upgrade-Insecure-Requests: 1
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.124 Safari/537.36


Headers when running in same host
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,image/apng,/;q=0.8,application/signed-exchange;v=b3;q=0.9
Accept-Encoding: gzip, deflate, br
Accept-Language: en-US,en;q=0.9,ta;q=0.8
Connection: keep-alive
Cookie: JazzFormAuth=Form; net-jazz-ajax-cookie-rememberUserId=; ASP.NET_SessionId=legwmrlennlocgdanfizc1cm; JSESSIONID=0000e0g5IEk6SriMj2lGCOdmd8h:caaab677-73c3-441d-9776-cd1ee7ece6c5; LtpaToken2=pt4ycwXvsUhV+BBvNBIiKOu1qe+wxZiU73kmk4zh3Xo4awNgc20ASECLNdBJQc/HkwW/rnPXbHbuenwfl8qUSrlQnKyVGWywukK9WJryR0j6TgA7Kxz3ga6eINrA7nd4r+MlJ2QAWQKaZ3FYMeLvx0Rp2PDonnEmWEB8GKSILagW/od9WDZM7c//Y27xecs2bCvtI51xeTMNw0vHZTveK7STWzOZ2w42xtjjcsinbAG26+1t1NUStt8g7WhiNvWvEygX4Yt+W2SH4HeyOzQK27q39xbmZbhy04LbFedDg9WxHyFDDTP67NPukF/1Nwir
Host: 172.xx.xx.xxx:9443
Referer: https://172.xx.xx.xxx/
sec-ch-ua: " Not;A Brand";v="99", "Microsoft Edge";v="91", "Chromium";v="91"
sec-ch-ua-mobile: ?0
Sec-Fetch-Dest: iframe
Sec-Fetch-Mode: navigate
Sec-Fetch-Site: same-site
Upgrade-Insecure-Requests: 1
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.114 Safari/537.36 Edg/91.0.864.54


Comments
Ralph Schoon commented Jun 30, 10:08 a.m. | edited Jun 30, 10:47 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

You should find the JSESSIONID in the Cookies. I am not sure if you have to pass it as a header yourself. I have looked into my examples and there the Cookie mechanism usually takes care of it.

One answer



permanent link
Jim Amsden (22837) | answered Jun 30, 3:13 p.m.

 You may be dealing with a CORS error.

Your answer


Register or to post your answer.