CXX-2480 documentation link cleanup

Use new docs URL, change mongodb.org to .com, fix dead links
---------

Co-authored-by: Ezra Chung <[email protected]>

Author: adriandole

README.md

@@ -26,7 +26,7 @@ for more details about the various versions of the driver.
 * [MongoDB C++ Driver Documentation](https://www.mongodb.com/docs/drivers/cxx/)
 * [MongoDB C++ Driver API Documentation](https://mongocxx.org/api/current/)
 * [MongoDB C++ Driver Contribution guidelines](https://mongocxx.org/contributing/)
-* [MongoDB Database Manual](https://docs.mongodb.com/manual/)
+* [MongoDB Database Manual](https://www.mongodb.com/docs/manual/)
 * [MongoDB Developer Center](https://www.mongodb.com/developer/languages/cpp/)
 * [StackOverflow](https://stackoverflow.com/questions/tagged/mongodb%20c%2b%2b)
 
@@ -50,11 +50,11 @@ Currently, no drivers guarantee API or ABI stability.
 
 ## MongoDB compatibility
 
-Compatibility of each C++ driver version with each MongoDB server is documented in the [MongoDB manual](https://docs.mongodb.com/drivers/cxx#mongodb-compatibility).
+Compatibility of each C++ driver version with each MongoDB server is documented in the [MongoDB manual](https://www.mongodb.com/docs/drivers/cxx#mongodb-compatibility).
 
 ## Bugs and issues
 
-See our [JIRA project](http://jira.mongodb.org/browse/CXX).
+See our [JIRA project](https://jira.mongodb.com/browse/CXX).
 
 ## License
 

THIRD-PARTY-NOTICES

@@ -4,7 +4,7 @@ be distributed under licenses different than the MongoDB software.
 In the event that we accidentally failed to list a required notice,
 please bring it to our attention through any of the ways detailed here:
 
-    https://jira.mongodb.org/browse/CXX
+    https://jira.mongodb.com/browse/CXX
 
 The attached notices are provided for information only.
 

docs/content/_index.md

@@ -33,7 +33,7 @@ Currently, no drivers guarantee API or ABI stability.
 
 ## MongoDB compatibility
 
-Compatibility of each C++ driver version with each MongoDB server is documented in the [MongoDB manual](https://docs.mongodb.com/drivers/cxx#mongodb-compatibility).
+Compatibility of each C++ driver version with each MongoDB server is documented in the [MongoDB manual](https://www.mongodb.com/docs/drivers/cxx#mongodb-compatibility).
 
 ## License
 

docs/content/getting-help.md

@@ -8,10 +8,10 @@ title = "Getting help"
 
 Often, the quickest way to get support for general questions is through
 the
-[MongoDB Community Forums](https://community.mongodb.com/tags/c/drivers-odms-connectors/7/cxx-driver)
+[MongoDB Community Forums](https://www.mongodb.com/community/forums/tag/cxx)
 or through
 [Stack Overflow](https://stackoverflow.com/questions/tagged/mongodb%20c%2b%2b).
 
 Please also refer to MongoDB's
-[support channels](https://docs.mongodb.com/manual/support) documentation.
+[support channels](https://www.mongodb.com/docs/manual/support) documentation.
 

docs/content/legacy-v1/breaking-changes.md

@@ -78,7 +78,7 @@ run all tests and client examples     |`test`
 * The driver will not function correctly unless `mongo::client::initialize` is invoked before using the driver APIs. The mongo::client::shutdown method should also be called at application termination (if options.callShutdownAtExit() is not set) so the driver can cleanly terminate. As a convenience, we have added [`mongo::GlobalInstance`](https://github.com/mongodb/mongo-cxx-driver/blob/legacy/src/mongo/client/init.h#L69) as an RAII wrapper to automatically call these methods.
 * options.callShutdownAtExit() is a no-op on non-static builds on Windows due to issues around sudden thread termination.
 * The driver no longer logs any output by default. You may configure and inject a logger to re-enable logging. See `src/mongo/client/examples/clientTest.cpp` for an example of how to enable logging.
-* Writes are now "[acknowledged](https://docs.mongodb.com/manual/core/write-concern/#write-concern-acknowledged)" by default. In all previous releases the default write concern was “[unacknowledged](https://docs.mongodb.com/manual/core/write-concern/#unacknowledged)”. This change may have performance and behavior implications for existing applications that did not confirm writes. You can read more about the change [here](https://docs.mongodb.com/manual/release-notes/drivers-write-concern/#driver-write-concern-change).
+* Writes are now "[acknowledged](https://www.mongodb.com/docs/manual/core/write-concern/#write-concern-acknowledged)" by default. In all previous releases the default write concern was “[unacknowledged](https://www.mongodb.com/docs/manual/core/write-concern/#unacknowledged)”. This change may have performance and behavior implications for existing applications that did not confirm writes. You can read more about the change [here](https://www.mongodb.com/docs/manual/release-notes/drivers-write-concern/#driver-write-concern-change).
 * The driver now throws a mongo::OperationException when write concern is greater than Acknowledged for errors that occur when running operations against a MongoDB database.
 * The default shutdown grace period is now zero which means the driver may block forever until a successful shutdown occurs.
 

docs/content/legacy-v1/configuration.md

@@ -151,7 +151,7 @@ if (!status.isOK()) {
 - Semantics: This flag only has an effect if `Options::current::SSLMode` is
   `Options::kSSLRequired`. If set, it specifies a file containing the
   certificate authority file to use. See the [MongoDB SSL
-  documentation](https://docs.mongodb.com/manual/tutorial/configure-ssl/#set-up-mongod-and-mongos-with-ssl-certificate-and-key)
+  documentation](https://www.mongodb.com/docs/manual/tutorial/configure-ssl/#set-up-mongod-and-mongos-with-ssl-certificate-and-key)
   for additional information on the CA file.
 
 #### `Options::setSSLPemKeyFile` and `Options::SSLPEMKeyFile`
@@ -161,7 +161,7 @@ if (!status.isOK()) {
 - Semantics: This flag only has an effect if `Options::current::SSLMode` is
   `Options::kSSLRequired`. If set, it specifies a file containing the SSL
   PEM key file to use. See the [MongoDB SSL
-  documentation](https://docs.mongodb.com/manual/tutorial/configure-ssl/#set-up-mongod-and-mongos-with-ssl-certificate-and-key)
+  documentation](https://www.mongodb.com/docs/manual/tutorial/configure-ssl/#set-up-mongod-and-mongos-with-ssl-certificate-and-key)
   for additional information on the PEM key file.
 
 #### `Options::setSSLPemKeyPassword` and `Options::SSLPEMKeyPassword`
@@ -173,7 +173,7 @@ if (!status.isOK()) {
   been set with `Options::setSSLPEMKeyFile`. If set, it specifies the
   password to be used to decrypt the SSL PEM key file specified with
   `Options::setSSLPEMKeyFile`. See the [MongoDB SSL
-  documentation](https://docs.mongodb.com/manual/tutorial/configure-ssl/#set-up-mongod-and-mongos-with-ssl-certificate-and-key)
+  documentation](https://www.mongodb.com/docs/manual/tutorial/configure-ssl/#set-up-mongod-and-mongos-with-ssl-certificate-and-key)
   for additional information on the PEM key file password.
 
 #### `Options::setSSLCRLFile` and `Options::SSLCRLFile`
@@ -183,7 +183,7 @@ if (!status.isOK()) {
 - Semantics: This flag only has an effect if `Options::current::SSLMode` is
   `Options::kSSLRequired`. If set, it specifies the file to use as the SSL
   certificate revocation list. See the [MongoDB SSL
-  documentation](https://docs.mongodb.com/manual/tutorial/configure-ssl/#set-up-mongod-and-mongos-with-ssl-certificate-and-key)
+  documentation](https://www.mongodb.com/docs/manual/tutorial/configure-ssl/#set-up-mongod-and-mongos-with-ssl-certificate-and-key)
   for additional information on the certificate revocation list file.
 
 #### `Options::setSSAllowInvalidCertificates` and `Options::SSLAllowInvalidCertificates`

docs/content/legacy-v1/installation.md

@@ -39,7 +39,7 @@ title = "Installing the legacy driver"
 ### How to ask for Help
 
 If you are having difficulty building the driver after reading the below
-instructions, please post on the [MongoDB Community Forums](https://community.mongodb.com/tags/c/drivers-odms-connectors/7/cxx-driver) to ask for
+instructions, please post on the [MongoDB Community Forums](https://www.mongodb.com/community/forums/tag/cxx) to ask for
 help. Please include in your post **all** of the following information:
 
  - The version of the driver you are trying to build (branch or tag).
@@ -169,7 +169,7 @@ have linked against libstdc++.
 There are several targets you can build, but the most common target for users of the library is `install`, which will build the driver, and install the driver and headers to the location specified with the `--prefix` argument. If no prefix is specified, `--prefix` defaults to a directory named ```build/install``` under the current source directory.
 
 ##### Client Feature Options
- - `--ssl` Enables SSL support. You will need a compatible version of the SSL libraries available.The default authorization mechanism since MongoDB version 3.0 is [SCRAM-SHA-1](https://docs.mongodb.com/manual/reference/program/mongo/). If you want to use standard MongoDB authentication, you should compile with --ssl option for SCRAM-SHA-1 mechanism support.
+ - `--ssl` Enables SSL support. You will need a compatible version of the SSL libraries available.The default authorization mechanism since MongoDB version 3.0 is [SCRAM-SHA-1](https://www.mongodb.com/docs/manual/core/security-scram/). If you want to use standard MongoDB authentication, you should compile with --ssl option for SCRAM-SHA-1 mechanism support.
  - `--use-sasl-client` Enables SASL, which MongoDB uses for the Kerberos authentication available on MongoDB Enterprise. You will need a compatible version of the SASL implementation libraries available. The Cyrus SASL libraries are what we test with, and are recommended.
  - `--sharedclient` Builds a shared library version of the client driver alongside the static library. If applicable for your application, prefer using the shared client.
 
@@ -324,7 +324,7 @@ scons
 
 ###### Building multiple Windows library variants:
 
-As of legacy-0.8, the Windows libraries are now tagged with boost-like ABI tags (see http://www.boost.org/doc/libs/1_55_0/more/getting_started/windows.html#library-naming), so it is possible to build several different variants (debug vs retail, static vs dynamic runtime) and install them to the same location. We have added support for autolib, so the selection of the appropriate library is handled automatically (see https://jira.mongodb.org/browse/CXX-200). To build all of the different driver variants, repeatedly invoke scons as follows:
+As of legacy-0.8, the Windows libraries are now tagged with boost-like ABI tags (see http://www.boost.org/doc/libs/1_55_0/more/getting_started/windows.html#library-naming), so it is possible to build several different variants (debug vs retail, static vs dynamic runtime) and install them to the same location. We have added support for autolib, so the selection of the appropriate library is handled automatically (see https://jira.mongodb.com/browse/CXX-200). To build all of the different driver variants, repeatedly invoke scons as follows:
 
 ```
 scons $ARGS install

docs/content/legacy-v1/tutorial.md

@@ -14,13 +14,13 @@ This is an introduction to usage of the MongoDB database from a C++ program.
 NOTE: this tutorial is for the legacy and 26compat versions of the C++ driver.
 
 First, install MongoDB – see the
-[installation](https://docs.mongodb.com/manual/installation/) page for
+[installation](https://www.mongodb.com/docs/manual/installation/) page for
 details.
 
 Next, you may wish to take a look at the [MongoDB
-Manual](https://docs.mongodb.com/manual/) for a language independent look at
+Manual](https://www.mongodb.com/docs/manual/) for a language independent look at
 how to use MongoDB. Also, we suggest some basic familiarity with the [mongo
-shell](https://docs.mongodb.com/manual/mongo/) – the shell is the primary
+shell](https://www.mongodb.com/docs/mongodb-shell/) – the shell is the primary
 database administration tool and is useful for manually inspecting the
 contents of a database after your C++ program runs.
 
@@ -43,7 +43,7 @@ The C++ driver includes several classes for managing collections under the paren
  - `DBClientConnection` is the connection class for connecting to a single MongoDB database server (or mongos)
  - `DBClientReplicaSet` is the connection class for connecting to a replica set.
 
-See the [API documentation](http://mongodb.github.io/api/1.0.2/) for
+See the [API documentation](https://mongodb.github.io/api/1.0.2/) for
 details on each of the above classes.
 
 #### A simple program that connects to the database
@@ -188,7 +188,7 @@ BSONObj DBClientWithCommands::getLastErrorDetailed();
 For an example, see [this demo](https://github.com/mongodb/mongo-cxx-driver/blob/legacy/src/mongo/client/examples/simple_client_demo.cpp).
 
 For additional background information on getLastError see the [write
-operations documentation](https://docs.mongodb.com/manual/core/write-operations/#write-concern).
+operations documentation](https://www.mongodb.com/docs/manual/core/write-operations/#write-concern).
 
 ### Count
 
@@ -279,7 +279,7 @@ server operation for each call. It's best practice to use this method
 sparingly, for example once at the beginning of your code, or perhaps in an
 external setup script that configures the database for your application.
 For more information about indexing, see the [MongoDB Indexing
-docs](https://docs.mongodb.com/manual/indexes/).
+docs](https://www.mongodb.com/docs/manual/indexes/).
 
 ### Sorting
 
@@ -323,7 +323,7 @@ db.update("tutorial.persons",
 The `update()` method can be used to modify specific fields, replace the
 entire existing document, insert new documents or update multiple
 documents.  In the MongoDB Manual, examples are provided in the [Modify
-Documents Tutorial](https://docs.mongodb.com/manual/tutorial/modify-documents/).
+Documents Tutorial](https://www.mongodb.com/docs/manual/tutorial/modify-documents/).
 
 ### Arrays
 
@@ -335,6 +335,6 @@ is available [here](https://github.com/mongodb/mongo-cxx-driver/blob/legacy/src/
 This overview just touches on the basics of using MongoDB from C++. There
 are many more capabilities. For further exploration:
 
- - See the language-independent [MongoDB Manual](https://docs.mongodb.com/manual/)
- - Experiment with the [mongo shell](https://docs.mongodb.com/manual/mongo/)
- - Review the [API docs](http://mongodb.github.io/api/1.0.2)
+ - See the language-independent [MongoDB Manual](https://www.mongodb.com/docs/manual/)
+ - Experiment with the [mongo shell](https://www.mongodb.com/docs/mongodb-shell/)
+ - Review the [API docs](https://mongodb.github.io/api/1.0.2)

docs/content/mongocxx-v3/_index.md

@@ -8,7 +8,7 @@ title = "The mongocxx (v3) driver"
 +++
 
 The mongocxx is a ground-up rewrite of a C++ driver for MongoDB based on
-[libmongoc](http://mongoc.org/).  It requires a C++11 compiler.  It is
+[libmongoc](https://mongoc.org/).  It requires a C++11 compiler.  It is
 known to build on x86 and x86-64 architectures for Linux, macOS,
 Windows, and FreeBSD.
 

docs/content/mongocxx-v3/client-side-encryption.md

@@ -8,17 +8,17 @@ title = "Client-Side Field Level Encryption with mongocxx"
 
 ## Client-Side Field Level Encryption
 
-New in MongoDB 4.2 [Client-Side Field Level Encryption (CSFLE)](https://docs.mongodb.com/drivers/use-cases/client-side-field-level-encryption-guide) allows administrators and developers to encrypt specific data fields in addition to other MongoDB encryption features.
+New in MongoDB 4.2 [Client-Side Field Level Encryption (CSFLE)](https://www.mongodb.com/docs/drivers/use-cases/client-side-field-level-encryption-guide) allows administrators and developers to encrypt specific data fields in addition to other MongoDB encryption features.
 
 With CSFLE, developers can encrypt fields client side without any server-side configuration or directives. Client-Side Field Level Encryption supports workloads where applications must guarantee that unauthorized parties, including server administrators, cannot read the encrypted data.
 
-For an overview of CSFLE, please read [the official MongoDB documentation in the manual](https://docs.mongodb.com/manual/core/security-client-side-encryption/).
+For an overview of CSFLE, please read [the official MongoDB documentation in the manual](https://www.mongodb.com/docs/manual/core/security-client-side-encryption/).
 
 ## Installation
 
 ### libmongocrypt
 
-Client-Side Field Level Encryption relies on a C library called `libmongocrypt` to do the heavy lifting encryption work. This dependency is managed by the C driver.  As long as the C driver installation is 1.16.0 or higher, and has been compiled with Client-Side Field Level Encryption support, this dependency should be managed internally.  See the C driver's [Using Client-Side Field Level Encryption](http://mongoc.org/libmongoc/current/using_client_side_encryption.html) for more information.
+Client-Side Field Level Encryption relies on a C library called `libmongocrypt` to do the heavy lifting encryption work. This dependency is managed by the C driver.  As long as the C driver installation is 1.16.0 or higher, and has been compiled with Client-Side Field Level Encryption support, this dependency should be managed internally.  See the C driver's [Using Client-Side Field Level Encryption](https://mongoc.org/libmongoc/current/client-side-field-level-encryption.html) for more information.
 
 ### mongocryptd
 
@@ -56,7 +56,7 @@ Automatic client-side field level encryption requires MongoDB 4.2 enterprise or
 
 ### Providing Local Automatic Encryption Rules
 
-The following example shows how to specify automatic encryption rules via the schema_map option. The automatic encryption rules are expressed using a [strict subset of the JSON Schema syntax](https://docs.mongodb.com/manual/reference/security-client-side-automatic-json-schema/).
+The following example shows how to specify automatic encryption rules via the schema_map option. The automatic encryption rules are expressed using a [strict subset of the JSON Schema syntax](https://www.mongodb.com/docs/manual/reference/security-client-side-automatic-json-schema/).
 
 Supplying a `schema_map` provides more security than relying on JSON Schemas obtained from the server. It protects against a malicious server advertising a false JSON Schema, which could trick the client into sending unencrypted data that should be encrypted.
 
@@ -89,7 +89,7 @@ Please see [`examples/mongocxx/automatic_client_side_field_level_encryption.cpp`
 
 The MongoDB 4.2 server supports using schema validation to enforce encryption of specific fields in a collection. This schema validation will prevent an application from inserting unencrypted values for any fields marked with the `"encrypt"` JSON schema keyword.
 
-It is possible to set up automatic client-side field level encryption using the `mongocxx::client_encryption` to create a new encryption data key and create a collection with the [Automatic Encryption JSON Schema Syntax](https://docs.mongodb.com/manual/reference/security-client-side-automatic-json-schema/).
+It is possible to set up automatic client-side field level encryption using the `mongocxx::client_encryption` to create a new encryption data key and create a collection with the [Automatic Encryption JSON Schema Syntax](https://www.mongodb.com/docs/manual/reference/security-client-side-automatic-json-schema/).
 
 ```c++
 // Please see the linked example below for full json_schema construction.