Use HTTPS links for Google domains in docs

docs/linux_debugging.md

 # Tips for debugging on Linux
 
 This page is for Chromium-specific debugging tips; learning how to run gdb is
 out of scope.
 
 [TOC]
 
 ## Symbolized stack trace
 
 The sandbox can interfere with the internal symbolizer. Use `--no-sandbox` (but
@@ skipping 62 matching lines @@
 the renderers won't be sandboxed. It is generally not an issue, except when you
 are trying to debug interactions with the sandbox. If that's what you are doing,
 you will need to attach your debugger to a running renderer process (see below).
 ***
 
 You may also want to pass `--disable-hang-monitor` to suppress the hang monitor,
 which is rather annoying.
 
 You can also use `--renderer-startup-dialog` and attach to the process in order
 to debug the renderer code. Go to
-http://www.chromium.org/blink/getting-started-with-blink-debugging for more
+https://www.chromium.org/blink/getting-started-with-blink-debugging for more
 information on how this can be done.
 
 #### Choosing which renderers to debug
 
 If you are starting multiple renderers then the above means that multiple gdb's
 start and fight over the console. Instead, you can set the prefix to point to
 this shell script:
 
 ```sh
 #!/bin/sh
@@ skipping 95 matching lines @@
 #### Single-Process mode
 
 Depending on whether it's relevant to the problem, it's often easier to just run
 in "single process" mode where the renderer threads are in-process. Then you can
 just run gdb on the main process.
 
     gdb --args chrome --single-process
 
 Currently, the `--disable-gpu` flag is also required, as there are known crashes
 that occur under TextureImageTransportSurface without it. The crash described in
-http://crbug.com/361689 can also sometimes occur, but that crash can be
+https://crbug.com/361689 can also sometimes occur, but that crash can be
 continued from without harm.
 
 Note that for technical reasons plugins cannot be in-process, so
 `--single-process` only puts the renderers in the browser process. The flag is
 still useful for debugging plugins (since it's only two processes instead of
 three) but you'll still need to use `--plugin-launcher` or another approach.
 
 ### Printing Chromium types
 
 gdb 7 lets us use Python to write pretty-printers for Chromium types. The
@@ skipping 177 matching lines @@
 locally now - and often nearly 100% of the time.
 
 ## Logging
 
 ### Seeing all LOG(foo) messages
 
 Default log level hides `LOG(INFO)`. Run with `--log-level=0` and
 `--enable-logging=stderr` flags.
 
 Newer versions of Chromium with VLOG may need --v=1 too. For more VLOG tips, see
-[the chromium-dev thread](http://groups.google.com/a/chromium.org/group/chromium-dev/browse_thread/thread/dcd0cd7752b35de6?pli=1).
+[the chromium-dev thread](https://groups.google.com/a/chromium.org/group/chromium-dev/browse_thread/thread/dcd0cd7752b35de6?pli=1).
 
 ### Seeing IPC debug messages
 
 Run with `CHROME_IPC_LOGGING=1` eg.
 
     CHROME_IPC_LOGGING=1 out/Debug/chrome
 
 or within gdb:
 
     set environment CHROME_IPC_LOGGING 1
@@ skipping 70 matching lines @@
 If you break in a debugger during a drag, Chrome will have grabbed your mouse
 and keyboard so you won't be able to interact with the debugger!  To work around
 this, run via `Xephyr`. Instructions for how to use `Xephyr` are on the
 [Running layout tests on Linux](layout_tests_linux.md) page.
 
 ## Tracking Down Bugs
 
 ### Isolating Regressions
 
 Old builds are archived here:
-http://build.chromium.org/buildbot/snapshots/chromium-rel-linux/
+https://build.chromium.org/buildbot/snapshots/chromium-rel-linux/
 (TODO: does not exist).
 
 `tools/bisect-builds.py` in the tree automates bisecting through the archived
 builds. Despite a computer science education, I am still amazed how quickly
 binary search will find its target.
 
 ### Screen recording for bug reports
 
     sudo apt-get install gtk-recordmydesktop
 
@@ skipping 38 matching lines @@
 [Running layout tests on Linux](layout_tests_linux.md) page.
 
 If you need to test something with hardware accelerated compositing
 (e.g., compiz), you can use `Xgl` (`sudo apt-get install xserver-xgl`). E.g.:
 
     Xgl :1 -ac -accel glx:pbuffer -accel xv:pbuffer -screen 1024x768
 
 ## Mozilla Tips
 
 https://developer.mozilla.org/en/Debugging_Mozilla_on_Linux_FAQ