Hi.
I have issue with site https://idp-industry.echa.europa.eu/idp/.
The site loads but "Login" button is not working. from browser log I can see Error 500 for js component: https://idp-industry.echa.europa.eu/idp/_fp
Seems the site is another CertPinner and can not work with SSL scanner 😞
Can someone confirm ? How to solve this not disabling SSL scanner ?
MWG version: 9.2.2
POST /idp/_fp HTTP/1.1
Host: idp-industry.echa.europa.eu
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:80.0) Gecko/20100101 Firefox/80.0
Accept: */*
Accept-Language: cs,en-US;q=0.7,en;q=0.3
Accept-Encoding: gzip, deflate, br
Content-Type: application/x-www-form-urlencoded; charset=UTF-8
X-Requested-With: XMLHttpRequest
Content-Length: 32
Origin: https://idp-industry.echa.europa.eu
DNT: 1
Connection: keep-alive
Referer: https://idp-industry.echa.europa.eu/idp/
Cookie: JSESSIONID=LBN0OCPW2M7jOKhkxp0jLHqf59tGPY-tEEuiY-DI.EPCECHA01526:idp-industry-server-7002; BIGipServerIDM_Production-idp-industry.echa.europa.eu-https-ext_pool=1006716426.23067.0000
Solved! Go to Solution.
Hello,
okay, but so you see the web site, which means that SSL is generally working.
Looks like the fetching the site works fine, but when you "POST" (e.g. login) the 500 is returned. This could also be caused by the web server, which we could check by making connection traces.
It might make sense to file an SR so we can take the connection traces and take a look what the web server responds. If possible we should look at a connection trace and a .har file exported from the developer console, in order to move forward.
Best,
Andre
Hi!
I can go there with SSL Scanner enabled and the object is loaded fine. When you use the developer tools and right click the blocked object saying "open in new tab", do you see an MWG error message?
If so, which one?
Andre
Hello,
okay, but so you see the web site, which means that SSL is generally working.
Looks like the fetching the site works fine, but when you "POST" (e.g. login) the 500 is returned. This could also be caused by the web server, which we could check by making connection traces.
It might make sense to file an SR so we can take the connection traces and take a look what the web server responds. If possible we should look at a connection trace and a .har file exported from the developer console, in order to move forward.
Best,
Andre
Corporate Headquarters
6220 America Center Drive
San Jose, CA 95002 USA