SSL certificate error with SAHI - proxy

I use SAHI for automated testing. Sahi has an internal proxy I use to interact with server application.
When I browse https websites, the proxy stores the sslcertificate. This certificate are self-signed and I have to import clicking on “Continue to this website (not recommended).”
It is boring but it but it works in many cases. Now I have to work with a hhtps site where this procedure doesn't work.
If i try to click on “Continue to this website (not recommended).”, nothing happen.
If I browse the site without proxy, I have no problems.
I use Win7, IE9.
Any idea?

If you are using the Open Source version of Sahi you could try the latest release of https://github.com/headissue/Sahi
since https://github.com/headissue/Sahi/releases/tag/v4.4.0-H7E it is possible to just click on the cert link on the startpage (s/dyn/Driver_initialized), then you never have to accept a certificate again.
I would appreciate if you try it out and feel free to contact me when you got any questions.

I didn't understand the reason of the problem, however I solved it just using Firefox.
With FireFox I can import the certificate just as usual, so I exported the certificate with FF than I importet it in IE and that's all.
Does any body know the reason of this issue?

Cause:
The website which you are trying to access may request resources from other domain other than the base domain(For base domain you have added the certificate while launching the URL)
Solution:
Open the developer tool goto network tab and search for any other domain and open the domain in a new tab, click "Proceed to website" (Chrome) or "I understand the risk" (firefox). Similarly do above steps for all the domains
Reload the page and check whether its displaying all the contents

Related

WAS Liberty adminCenter login displays login.css page

I have configured my Websphere Liberty server to support the Admin Center as described in the IBM Knowledge center.
I am running WAS Liberty version 17.0.0.1 on Windows 10 from an eclipse Neon environment (ie. on localhost). I connect with the URL (http://localhost:9080/adminCenter) from Chrome (version 61).
It puts up a login page (not great looking but serviceable)
I enter my credentials and click Submit and I am taken to the login.css webpage.
Within the Chrome developer tools, I can see an error message on the console indicating the GET for favicon.ico failed.
Then I can go to the browser address bar, manually change the URL to point to the adminCenter and it takes me to the Toolbox page for the Admin Center. From there I can select the Server Config graphic and see my server data.
Can anyone identify what I have configured wrong that is causing the AdminCenter to display the login.css webpage rather than re-route to the adminCenter webpage after I login?
Additionally, if anyone can direct me to instructions on how to put up a more user-friendly login page, I would be very grateful. (I'm doing my client-side application development in Angular. The only information I've found so far for customizing a login page with WAS Liberty references creating a login jsp page which I don't know how to do. (Sorry, I don't have enough reputation points to provide the URL for this) I'm still learning Angular and client-side development.)
Have you previously accessed a different version of Liberty and accessed its Admin Center on that browser? If so, your browser (or something else in the network pipe) could be caching old files causing such issues. When something like that happens, easiest way to check would be to try and open the page (the url you're using is correct, and it correctly redirects you to HTTPS) in a private/incognito tab/window of the browser (ctrl+shift+n for most browsers), or a different browser. Alternatively, you can clear the cache of the browser you're using for that page/domain (which would also be the actual fix if the cache is indeed the problem.)

Testing Pinterest with Jmeter

I've succesfully installed Jmeter and setup the recording. I added the next config elements: HTTP Cookie Manager, HTTP Cache Manager with clear cache every iteration enabled. I'm using Firefox and Jmeter is recording everything that I do in the browser.
But I have one problem: when I go to pinterest.com I receive a white page with black text. Every other website is working like it suppose, but I want to test only Pinterest. When I try to setup a new account...the same: white page with black text. Something is not loading correctly and I don't know what.
Can someone help me with a hint?
When you to through the proxy, your browser doesn't trust HTTPS traffic anymore, because the proxy replaces the certificates. If your page is a HTTP page that uses HTTPS resources like Style Sheets or JS files, you get what you're describing - a plain black text site on white background - where graphic buttons don't work anymore.
If you use firebug to inspect your traffic, you will see the resources that are not loading because of HTTPS certificate issues. You can either add exceptions to your browser to load these resources, or as #aleix suggested you can use a browser plugin like Blazemeter to record scripts without going through a proxy.
See here for more information.
Thank you all for answering to my problem. I've resolved the issue by importing manually the certificate created by Jmeter in his bin folder to Firefox.
It was, indeed, a https certificate problem, but I'd managed it because of your feedback.
Try blazemeter extension for chrome, is a recorder http request like proxy server of JMeter, and maybe it wil allow you to record correctly in pinterest

open ssrs report in an iframe

I have developed a website which runs at SSL (https). I want to open some SSRS reports at the website in an iframe. But it is not opened since browsers say that "Blocked loading mixed active content" in the browser's console.If I hit report's URL in another tab or another browsers window then it opens.Also if I run my website at http only then browser opens the report in the iframe perfectly at the website.I think this problem is arises since website runs on https and report url is http only.
What can I do to resolve this issue without change in any of the URL.
Thanks in advance.
What version of SSRS are you using? It is possible to install multiple instances of SSRS on the same machine. They may not have access to the same sets of reports, but I'm not sure if that would even be an issue for you. The configuration you are attempting seems a bit messy. Personally I would try to get all of the sites on SSL to be consistent, but that sounds like you may not be able to achieve that, politically.
Anyway, here's a link to get you started with the multiple SSRS instance approach, if you'd like to try it.
http://technet.microsoft.com/en-us/library/ms403426(v=sql.90).aspx

firefox has blocked content that isn't secure

I am running a site. Some of its pages are not working in Firefox, but work perfect in Chrome. In Firefox it shows me a gray shield next to the URL and when I click on that shield and manually click on disable protection on this page then my page works fine. So now the problem is that there are many users on my site, and some of them don't know how to do it so I want to handle it on my site so its users don't need to do that.
How can I do it? I Googled and found a setting of Firefox in about:config named security.mixed_content.block_active_content. If we set it to false then it works. So is there a way to do it programmatically or other way so that users just view that page without seeing that shield?
As I understand it, content that is blocked by default by Firefox now is http content that is accessed from an https page. Common types of content that fall foul of this are external stylesheets and images.
As far as I am aware the way to prevent the problem on your site is to make sure that if a page is served by https, any and all other files that it references are also served by https.
Hi Friends,
The reason you see this error in Mozilla Firefox is because your
website is a Mixed Box that is, your website has many internal links
which are not SSL protected.
In order to avoid this error from showing up in Mozilla Firefox you
will have to make sure all the internal links on your website are SSL
protected.
So, Use https:// in your page not http://
I hope I was clear enough in answering your query.
firefox has blocked content that isn't secure means there are some contents on your website are not secure.
I had same issue as my fonts were downloading with http://google.apis.something instead of https
Then I change to //google.apis.something and problem get solved.
To know what is not secure in you website use this link

How do you get the File:// protocol to work in IE8?

I am running a website on my local machine ("http://localhost/asdf") and trying to get some file:// protocol links to work. In reality I'm trying to open a folder, not a specific file, but I can't get either to work.
I've put localhost in my "trusted zone", I've tried every combo of "file" ,":", some number of "/" and then a whole bunch of different paths, but encoded and not encoded.
Nothing I do causes anything to open when I click on the link. If I copy the link destination, and paste that in the browser address window, then it works as expected.
Anyone know the secret?
Add your intranet site in the Intranet Zone in Security Tab.
Generally file:/// URLs shouldn't work on pages downloaded via HTTP, that they sometimes work in IE7 and earlier is a security issue.
We found that window.open method using the file protocol in the URL causes the method to fail. Under I.E. the behavior is erratic. In some instances, the object mentioned in the URL is opened but the window object instance is not created. In others, the URL failes to open. In some instances we noted that under Windows 7, the URL opens, under XP it does not. Under Safari,Chrome and Firefox, the URL never opened.
Local server is something different than just file://, that should work in IE as it is. However, if you probably want to check out apache alias and link that folder to your server. Btw, you should not use file protocol anyway, it will not work on production.

Resources