Chrome behaviour after accepting untrusted certificate - google-chrome

I currently meet some issue with Chrome behaviour.
My company is using self certificate product on the internal network where are hosted our applications.
My users are following the current steps:
Going on the website, accept the "untrusted certificate"
Using the app X time
Clicking on one button making an Ajax Call to get images on the Apache server
Ajax calls are resulting in a 404 failed request
I figured out that I can reproduce this behaviour by "Re-enabling" the warning before to click on the button making the Ajax Call:
There is my questions:
Is it possible that chrome is "Re-enabling" the warning automatically after X times ? If yes how many time ? And where can I find more informations about this subject ?
Is there an option to disable Chrome to "Re-enable" the warning by itself ? If yes how ?
Thank you.

Related

Google analytics hit returns 302 and second request wont work

So basically the first hit is returning 302 and the user agent (in this case my web browser) is invited to send the SAME hit again to another url but this time even when im getting a 200 the hit is sent incorrectly because lots of the params are not being send. (This happens sometimes not always)
First Hit:
Second Hit:
To clarify a little more im getting this problem with an addToCart (EE) and its causing me to products sales without being added to cart. I checked the dataLayer and everything seems to be ok.
So im in doubt if its a problem with my web browser or its a problem with analytics?
If version of the web browser are needed you can read it on the user-agent of the images.
I had the same issue when I tried to manually insert the google analytics tracking code(gtag) in my .
First step was to remove the Google analytics code from the header. I had used the plugin 'Insert Headers and Footers'.
Afterwards I installed Insights Monster plugin, went through the launch wizard and the 302 redirect disappeared.
I didn't really want to use a heavy plugin to resolve this issue but unfortunately it was the only solution for me.
I copied and answer from here: https://tonnygaric.com/blog/prevent-google-analytics-from-making-requests-to-stats-g-doubleclick-net you need to do a configuration in Google Analytics dashboard.
The answer is pretty simple. Go to GA -> Admin -> Tracking info -> Data Collection -> disable both toggles and click on save. It can take up to 24 hours for the changes to take effect.

The cookie alert for allowing customers to save the cookies repeats and navigates to Enable Cookies page in Google Chrome

I am new to Magento and I have just setup Magento 1.8.1 with the sample data. I was going through the user guide of Magento CE 1.8.1 and came to know that Cookie restriction mode should be set to Yes because of European Union Privacy and Electronic Communications Directive and its amendment. But i am facing a issue now which I am unable to resolve. After changing the settings to Yes, I refreshed my site and I got the Allow Cookie Alert Box. I clicked Allow and I was directed to the Enable Cookies page. I again clicked allow on that page and was directed back to the same page as if it just refreshed. I am embedding screenshots for clear understanding:
the first one is the home page and the second one is the enable cookie page.
Few changes what I did was, I changed System -> Config -> General -> Web -> use http only to No. I did this because I was getting errorless Login page when I was trying to login on the backend in Google chrome and this was one of the solutions available on stack overflow. But I reverted this back to yes when I came to know that this makes the site vulnerable to attacks. That's why I did some changes in the varien.php file as described in the second solution of Why I can not login to magento backend using google chrome by a user named AKT. Also, I had set the Cookie Restriction Mode to YES. Does anyone have a solution to this? This is only happening in Google Chrome.

500 Internal Server Error just on Google Chrome when logging into PayPal

Whenever I try to visit log in to PayPal on Google Chrome (my current version is 35.0.1916.114 which is the most up to date at the time of writing this), I get a 500 Internal Server Error. Here's the exact one:
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator, webmaster#paypal.com and inform them of the time the error occurred, and anything you might have done that may have caused the error.
More information about this error may be available in the server error log.
I'm able to visit the homepage fine and I can log in on all other browsers but this has been an issue for some time now (I just haven't gotten around to looking into it). At the moment, I open Firefox just to use PayPal but I used Chrome for everything else so I'm trying to solve it.
Any ideas on why this would be happening? I've seen other questions on the web similar but they are mainly due to people 'buying' through PayPal which isn't a problem for me. I can purchase items on the 'purchase' screens that you get redirected to from a site.
Thanks for your help!
I see this from time to time on a couple of very specific web sites (e.g., Slashdot). All other sites works fine when this happens (and the site works fine in other browsers, including Web Kit based ones). The embarrassingly simple solution is to restart the browser (I try to avoid it since I often have 50+ tabs open). If guess the problem might be session cookies (that would explain why a restart works). As a consequence of this guess, clearing all permanent cookies for PayPal and related sites might be worth considering.
For me, I do like this at the 500 error page
Click on the Secure to the left side of the address bar
Select Site settings
Select Reset site settings at the bottom of the page
Reload the page
in some cases but not all. There appears to be a corrupt session via the cookie or data stored for a specific browser in the java files. Try the following;
1. Download CCleaner (close chrome)
Remove and clean registry files
Remove tmp and cached for CHROME as well as cookies
Clear index.dat file
4. Control Panel / Java-open / clear internet java cached files
5. Make sure you're not using a proxy IP for the web
6. Restart computer
7. Try again
Now that Google separated cookies from permissions I had to delete my cookies separately to get it to work.
Click on the Secure to the left side of the address bar
Select Cookies
Select the wordpress cookies and Remove each one
Reload page

Why is Chrome calling the autocompleted url before validation?

I'm using an API on my website to send emails to the users and while testing my call I noticed I was receiving the email twice.
So the url looks like "localhost/api/sendEmail" and, at least on Chrome, when I'm on localhost and I start typing "/ap" the url is automatically completed.
And I can see on Fiddler that Chrome (well I think that's him) is actually calling it before I press Enter so the mail is sent, and when I press Enter it is of course sent a second time.
This is not a problem since it won't be directly callable by the end-user, but I was just wondering what is the purpose of this first call ? Is Chrome pre-calling the page to make it faster to load ? Can it cause problems in different situations? Can one prevent Chrome from behaving like this?
Again, not a problem at all, but I'm just wondering.
This is Google's prefetch feature, which loads the page quicker, assuming you execute the auto-completed URL.
You can disable this option in Google Chrome:
Settings > Advanced Settings > Privacy: (uncheck) Prefetch resources..
Update 2019
I came across a similar question on superuser, which I provided an updated answer for.
Disable page load prediction service
chrome://settings/ -> expand Advanced section
Disable NoState Prefetch
chrome://flags -> search for "nostate"

Chrome extension losing requested permissions after browser restart

I developed a chrome extension which communicates with IP phones.
The communication is done in a event page which is sending POST requests via the XMLHttpRequest object.
Because the hostname or IP address of the phone is configured in the options page I added optional_permissions to the manifest file and request them from the user after saving the options with chrome.permissions.request.
Cross-Origin XHR works now without any problems until I restart chrome...
After restarting chrome it seems like the requested permission is lost and I get the typical
is not allowed by Access-Control-Allow-Origin error.
When I click on the extensions permissions I can also see that my requested permission is no longer listed.
Because the chrome.permissions.request is only working for a user gesture I can't request it during the load of my extension or on the fly. If I request the permission again in my options page I don't get asked again whether I want to allow it or not put the permission is granted and everything works again as usual.
Is there a way to get this permission granted persistent after requesting it? I only want the extension to have access to the endpoints it needs.
Thank you very much.
For me the following reported issue answered my question:
Issue 158004: chrome.permissions.request support for user-supplied URL.
To make it clear: It is not possible to request a subset of the permissions defined in optional_permissions. If you define http://*/* then you need to request exactly this string! A subset like http://example.org/* wont work!
Here is a quote from a comment in the issue description which makes that clear:
"There's no wildcard handling, just plain string comparison between the URLPatterns"
The Issue has been fixed in Revision 182287
The only thing left is to cross your fingers that this fix gets included in a upcomming chrome release soon. We'll have to use the bloody Access your data on all websites permission in the meanwhile.