diff --git a/_assetsApi/metadata-config.json b/_assetsApi/metadata-config.json new file mode 100644 index 0000000..c501fcc --- /dev/null +++ b/_assetsApi/metadata-config.json @@ -0,0 +1,13 @@ +{ + "metadata": [{ + "src": [ + { + "files": [ + "src/**.dll" + ] + } + ], + "dest": "metadata", + "filter": "filterConfig.yml" + }] +} diff --git a/_config.yml b/_config.yml deleted file mode 100644 index cbe4cbd..0000000 --- a/_config.yml +++ /dev/null @@ -1,96 +0,0 @@ -# The public documentation URL, used for sitemap.xml -url: "https://docs.telerik.com/fiddlercore" - -# Exclude files which should not be in the output -exclude: [README.md, Gemfile, Gemfile.lock] -exclude_navigation: ["knowledge-base/*"] - -## List your directory names and order here, like this: -navigation: - getting-started: - title: Getting Started - position: 10 - - basic-usage: - title: Basic Usage - position: 20 - - knowledge-base: - title: Knowledge Base - position: 100 - - licensing: - title: Licensing - position: 200 - -## An exprerimental property to resolve th SEO vs STA panels conflicts -## Discussed in the folllowing issue: https://github.com/telerik/docs-seed/issues/159 -## Build only with docs-seed branch #fiddler-page-title -page_title_product: "FiddlerCore" -use_product_in_title: true - - -## Product title -product: "Progress Telerik FiddlerCore" -platform: fiddler-core - -## The application virtual path -baseurl: /fiddlercore - -## Assign layout and category per different paths -defaults: -- - scope: - path: "" - values: - layout: "documentation" - category: "default" - product: "fiddlercore" - editable: true - -has_kb_portal: true -has_api_reference: true - - -productCode: FIDDLERCORE - -# The google services configuration -google_analytics: UA-111455-1 -google_tag_manager: GTM-6X92 -gcs_engine: '001595215763381649090:bhf815yqanw' -gcs_api_key: 'AIzaSyDWHnF6UKhvS44zCVYggJysw98qCaInqiE' - -edit_repo_url: https://github.com/telerik/fiddler-core-docs/edit/master - -footer: -- - title: "Getting Started" - links: - "Try Now": https://www.telerik.com/download/fiddlercore -- - title: "Community" - links: - "Forums": https://www.telerik.com/forums/fiddler - "Blogs": https://www.telerik.com/blogs/tag/fiddler - "Feedback Portal": https://feedback.telerik.com/fiddlercore - -footer_social: - facebook: https://www.facebook.com/Telerik/ - youtube: https://www.youtube.com/user/TelerikInc - linkedin: https://www.linkedin.com/showcase/telerik/ - twitter: https://twitter.com/TelerikFiddler/ - -api_reference_url: "api/" - -# Assets pipeline configuration -assets: - cachebust: soft - js_compressor: uglifier - -## Do not edit below this line -safe: false -markdown: MarkdownProcessor -kramdown: - toc_levels: 2..3 - smart_quotes: ["quot", "quot", "quot", "quot"] - input: GFM diff --git a/basic-usage/capture-https-traffic.md b/basic-usage/capture-https-traffic.md index 2e02213..07a6879 100644 --- a/basic-usage/capture-https-traffic.md +++ b/basic-usage/capture-https-traffic.md @@ -11,7 +11,7 @@ position: 30 This article explains how to capture HTTP/S traffic with FiddlerCore -Once FiddlerCore is [configured]({%slug configuration %}), it starts to listen for a traffic on the background. When it captures any session, it notifies you by raising the following events: +Once FiddlerCore is [configured](slug://configuration), it starts to listen for a traffic on the background. When it captures any session, it notifies you by raising the following events: >tip The following event handlers are invoked on session-handling **background threads**. > @@ -46,7 +46,8 @@ You should use this event to act when a session is completed. For example, notif Console.WriteLine($"Finished session: {session.fullUrl}"); } ``` ->tip These are only the most commonly used handlers. For the full list of events check [FiddlerApplication's API reference](/api/fiddler.fiddlerapplication). + +>tip These are only the most commonly used handlers. For the full list of events check FiddlerApplication's API reference. ## FiddlerApplication.ClientCertificateProvider @@ -59,4 +60,4 @@ FiddlerApplication.ClientCertificateProvider = localCertificateSelectionCallback ## Next Steps -- [Import/export sessions]({%slug import-export-sessions%}) +- [Import/export sessions](slug:// import-export-sessions) diff --git a/basic-usage/configuration.md b/basic-usage/configuration.md index 62c5cb4..ac8df32 100644 --- a/basic-usage/configuration.md +++ b/basic-usage/configuration.md @@ -50,6 +50,7 @@ class Program To configure FiddlerCore, you can use `FiddlerCoreStartupSettingsBuilder` class, which encapsulates the logic for creating `FiddlerCoreStartupSettting` instance, which in turn can be used as an argument for `FiddlerApplication.Startup(FiddlerCoreStartupSettings)` method. `FiddlerCoreStartupSettingsBuilder` provides fluent API, for example a convenient usage is: + ```c# FiddlerCoreStartupSettings startupSettings = new FiddlerCoreStartupSettingsBuilder() @@ -74,7 +75,6 @@ FiddlerApplication.AfterSessionComplete += session => { Console.WriteLine($"Finished session: {session.fullUrl}"); } - FiddlerApplication.Startup(startupSettings); ``` @@ -89,7 +89,7 @@ The following configuration methods of `FiddlerCoreStartupSettingsBuilder` are a #### System proxy settings: -> There are a lot of possible systems and types of connections which might have to be modified in order to set proper proxy settings, and the following methods handle only the most common scenarios. For more advanced proxy configuration, see [Register as System Proxy]({%slug register-as-system-proxy %}) article. +> There are a lot of possible systems and types of connections which might have to be modified in order to set proper proxy settings, and the following methods handle only the most common scenarios. For more advanced proxy configuration, see [Register as System Proxy](slug://register-as-system-proxy) article. - `RegisterAsSystemProxy()`: Modifies the local LAN connection's proxy settings to point to the port on which FiddlerCore is listening on localhost. - `MonitorAllConnections()`: Modifies all system connections' proxy settings to point to the port on which FiddlerCore is listening on localhost. @@ -108,14 +108,15 @@ FiddlerApplication.Prefs.SetStringPref("fiddler.proxy.pacfile.text", "return 'PR #### Other settings: - `EnableHTTP2()`: Enables the support for capturing HTTP/2 traffic. Available with FiddlerCore version 6.x.x and above. -- `DecryptSSL()`: Enables decryption of HTTPS traffic. You should have a CertificateProvider loaded with trusted certificate. For more details see [Use Custom Root Certificate]({%slug use-custom-root-certificate %}) article. +- `DecryptSSL()`: Enables decryption of HTTPS traffic. You should have a CertificateProvider loaded with trusted certificate. For more details see [Use Custom Root Certificate](slug://use-custom-root-certificate) article. - `UseClientTlsProvider(IClientTlsConnectionProvider customClientTlsProvider)`: Sets a custom client TLS provider for Fiddler. The provider will be used to authenticate an existing connection and return a stream to read/write data from/to it. Available with FiddlerCore version 6.x.x and above. ## Handling Events -The `FiddlerApplication` class exposes numerous events like `BeforeRequest`, `BeforeResponse`, `AfterSessionComplete`, and many more. Full list of all supported events can be found in the [FiddlerCore API reference](https://docs.telerik.com/fiddlercore/api/fiddler.fiddlerapplication#events). + +The `FiddlerApplication` class exposes numerous events like `BeforeRequest`, `BeforeResponse`, `AfterSessionComplete`, and many more. Full list of all supported events can be found in the FiddlerCore API reference. -Learn more on how to use the FiddlerCore events in the [Capture HTTP/S Traffic]({%slug capture-https-traffic %}) article. +Learn more on how to use the FiddlerCore events in the [Capture HTTP/S Traffic](slug://capture-https-traffic) article. ## Shutdown @@ -125,5 +126,5 @@ FidlerCore can be shut down using the following method of `FiddlerApplication` ## Next Steps -- [Register as System Proxy]({%slug register-as-system-proxy %}) -- [Use Custom Root Certificate]({%slug use-custom-root-certificate %}) +- [Register as System Proxy](slug://register-as-system-proxy) +- [Use Custom Root Certificate](slug://use-custom-root-certificate) diff --git a/basic-usage/import-export-sessions.md b/basic-usage/import-export-sessions.md index 17688fc..cbe2319 100644 --- a/basic-usage/import-export-sessions.md +++ b/basic-usage/import-export-sessions.md @@ -14,21 +14,21 @@ This article explains how to import and export sessions with FiddlerCore. You can import sessions with FiddlerCore by using the following code: ```c# - Session[] loaded = Utilities.ReadSessionArchive(sazFilename, false, "", (file, part) => - { - Console.WriteLine($"Enter the password for { part } (or just hit Enter to cancel):"); - string sResult = Console.ReadLine(); - Console.WriteLine(); - - return sResult; - }); +Session[] loaded = Utilities.ReadSessionArchive(sazFilename, false, "", (file, part) => +{ + Console.WriteLine($"Enter the password for { part } (or just hit Enter to cancel):"); + string sResult = Console.ReadLine(); + Console.WriteLine(); + + return sResult; +}); ``` ## Export Sessions You can export sessions with FiddlerCore by using the following code: ```c# - bool success = Utilities.WriteSessionArchive(filename, sessions.ToArray(), password, false); +bool success = Utilities.WriteSessionArchive(filename, sessions.ToArray(), password, false); ``` >tip With FiddlerCore version 6.0.0 and above, the SAZ archive will contain additional information about various metrics, such as timings and sizes, through the `SessionMetrics` class. @@ -37,5 +37,5 @@ You can export sessions with FiddlerCore by using the following code: There are cases when you may want to use custom provider to save FiddlerCore sessions. You do this by setting the following property: ```c# - FiddlerApplication.oSAZProvider = new CustomSazProvider(); +FiddlerApplication.oSAZProvider = new CustomSazProvider(); ``` diff --git a/basic-usage/register-as-system-proxy.md b/basic-usage/register-as-system-proxy.md index 208d00f..764fe4c 100644 --- a/basic-usage/register-as-system-proxy.md +++ b/basic-usage/register-as-system-proxy.md @@ -23,7 +23,7 @@ FiddlerCoreStartupSettings startupSettings = FiddlerApplication.Startup(startupSettings); ``` -There are more basic methods affecting the system proxy settings in the FiddlerCoreStartupSettings. You can read more in [Configuration/Proxy settings]({%slug configuration %}#system-proxy-settings) article. +There are more basic methods affecting the system proxy settings in the FiddlerCoreStartupSettings. You can read more in [Configuration/Proxy settings](slug://configuration#system-proxy-settings) article. ## Advanced approach Instead of using the basic configuration methods, you can manually modify the proxy settings. The logic for modifying the system connections' proxy settings is separated in the Telerik.NetworkConnections assembly. @@ -61,5 +61,5 @@ The following default implementations for `INetworkConnectionsDetector` are prov ## Next Steps -- [Capture HTTP/S Traffic]({%slug capture-https-traffic %}) +- [Capture HTTP/S Traffic](slug://capture-https-traffic) diff --git a/basic-usage/use-custom-root-certificate.md b/basic-usage/use-custom-root-certificate.md index 9609826..c6a522f 100644 --- a/basic-usage/use-custom-root-certificate.md +++ b/basic-usage/use-custom-root-certificate.md @@ -59,4 +59,4 @@ The following code explains how to trust your root certificate. ## Next Steps -- [Import/export sessions]({%slug import-export-sessions%}) +- [Import/export sessions](slug://import-export-sessions) diff --git a/docs-builder.yml b/docs-builder.yml new file mode 100644 index 0000000..3a6d1ce --- /dev/null +++ b/docs-builder.yml @@ -0,0 +1,57 @@ +top-navigation-product: fiddler-core +path-prefix: /fiddler/fiddlercore/documentation +default-title-prefix: FiddlerCore + +primary-color: "#27c106" # Fiddler green + +product-id: 1608 +product-code: FIDDLERCORE +product-name: Progress Telerik FiddlerCore +product-url: https://www.telerik.com/fiddlercore +product-trial-url: https://www.telerik.com/try/fiddlercore + +contribute-url: https://github.com/telerik/fiddler-core-docs/edit/master + +search-engine-id: 001595215763381649090:bhf815yqanw # TODO get a new one for FiddlerCore +# where should we add the google analytics and tag manager codes (refer to _config.yml)? +avatar-path: ./images/common/avatar-ninja.svg # TODO get a FiddlerCore NINJA +no-results-image-path: ./images/common/no-results.svg # TODO get a FiddlerCore no-results.png +table-layout: fixed +enable-tabbed-code-blocks: true + +gitLastCommitDateEnabled: true + +cta-overview: '@ProductLink is a powerful .NET library that allows you to capture and modify HTTP and HTTPS traffic.' +cta-intro: '@ProductLink is a FiddlerCore is a .NET class library you can integrate into your .NET applications. Its available in .NET Standard 2.0, .NET Framework 4.0, and .NET Framework 4.5 flavors, which allows using it on Windows, Linux, Mac, and any other platform implementing .NET Standard.' + +img-max-width: 100% +center-images: false + +meta: + '*': + hideCta: true #consult if we want to hide the CTA on all pages (currently incorrectly sjhowing 30-days trial for Fiddler Everywhere) + getting-started: + title: Getting Started + position: 10 + basic-usage: + title: Basic Usage + position: 20 + knowledge-base: + title: Knowledge Base + position: 100 + relativeUrl: /knowledge-base + hideChildren: true + res_type: kb + licensing: + title: Licensing + position: 200 + api: + title: API Reference + position: 300 + relativeUrl: /api + hideChildren: true + res_type: api + +redirects: +- from: ^/$ + to: /introduction diff --git a/getting-started/download-product-files.md b/getting-started/download-product-files.md index 2fa8592..1e4e566 100644 --- a/getting-started/download-product-files.md +++ b/getting-started/download-product-files.md @@ -41,4 +41,4 @@ Below you could find a list of the available files: ## Next Steps -- [FiddlerCore Configuration]({%slug configuration%}) +- [FiddlerCore Configuration](slug://configuration) diff --git a/getting-started/first-steps.md b/getting-started/first-steps.md index d99fd5e..9452709 100644 --- a/getting-started/first-steps.md +++ b/getting-started/first-steps.md @@ -13,15 +13,18 @@ This article explains everything you need to know about FiddlerCore before you s ## System Requirements -You can check the requirements for FiddlerCore suite in the [System Requirements]({%slug system-requirements%}) help article. +You can check the requirements for FiddlerCore suite in the [System Requirements](slug://system-requirements) help article. ## Download FiddlerCore See how to download the library in the following help articles: -* [Download Product Files]({%slug download-product-files%}) -* [Use Telerik NuGet Server]({%slug telerik-nuget-server%}) +* [Download Product Files](slug://download-product-files) +* [Use Telerik NuGet Server](slug://telerik-nuget-server) ## Next Steps -[Check the system requirements]({%slug system-requirements%}) \ No newline at end of file +[Check the system requirements](slug://system-requirements) +[Using API Key to get FiddlerCore from Nuget](slug://telerik-nuget-sso) +[Basic FiddlerCore configuration](slug://configuration) +[Capturing HTTPS traffic with FiddlerCore](slug://capture-https-traffic) \ No newline at end of file diff --git a/getting-started/images/nuget-keys-telerik-001.png b/getting-started/images/nuget-keys-telerik-001.png index 9f94179..bae6e4b 100644 Binary files a/getting-started/images/nuget-keys-telerik-001.png and b/getting-started/images/nuget-keys-telerik-001.png differ diff --git a/getting-started/system-requirements.md b/getting-started/system-requirements.md index e8dc041..14e577f 100644 --- a/getting-started/system-requirements.md +++ b/getting-started/system-requirements.md @@ -37,5 +37,5 @@ In order to develop applications with **Telerik FiddlerCore** you need to have t ## Next Steps -* [Download Product Files]({%slug download-product-files%}) -* [Use Telerik NuGet Server]({%slug telerik-nuget-server%}) +* [Download Product Files](slug://download-product-files) +* [Use Telerik NuGet Server](slug://telerik-nuget-server) diff --git a/getting-started/nuget-sso.md b/getting-started/telerik-api-keys.md similarity index 55% rename from getting-started/nuget-sso.md rename to getting-started/telerik-api-keys.md index eb2d433..b00df99 100644 --- a/getting-started/nuget-sso.md +++ b/getting-started/telerik-api-keys.md @@ -1,45 +1,46 @@ --- -title: Generating and Using Telerik NuGet Key +title: Generating and Using Telerik API Key description: Learn how to use API keys for authentication with the Telerik NuGet server when you have an SSO account and cannot use a username and password. slug: telerik-nuget-sso position: 100 +previous_url: /nuget-sso --- -# Generating and Using Telerik NuGet Key +# Generating and Using Telerik API Key -Progress Telerik expanded the account sign-in and login options, and now you can create a Telerik account through Google Authentication or by using custom SSO providers. While that change aims to ease the accessibility and usage of the whole Telerik system, it also presents a challenge for those who want to use a NuGet library through the Telerik NuGet server. +Progress Telerik expanded the account sign-in and login options, and now you can create a Telerik account through Google Authentication or by using custom SSO providers. Additionally, the Telerik API key is the default authentication method while using the Telerik NuGet server. -## Why and How to use a NuGet Key +## Why and How to use a API Key The main reason is that you can quickly and efficiatenly set your NeGut key within the application configuration and forget about Nuget credentials. -Additionally, some Telerik products (like [FiddlerCore](https://docs.telerik.com/fiddlercore/getting-started/telerik-nuget-server) or [Kendo UI](https://docs.telerik.com/kendo-ui/intro/installation/nuget-install)) are available through the Telerik NuGet server which requires authentication. Until recently, you could only use your Telerik account credentials to authenticate with the Telerik NuGet server. However, a Telerik account that uses Google Authentication or custom SSO will notice no direct SSO login option to access the NuGet servers, and entering a username & password is a no-go. Luckily, the Progress Telerik team developed NuGet keys which can be used instead of the conventional username & password paradigm. +Additionally, some Telerik products like [FiddlerCore](https://docs.telerik.com/fiddlercore/getting-started/telerik-nuget-server) or [Kendo UI](https://docs.telerik.com/kendo-ui/intro/installation/nuget-install) are available through the Telerik NuGet server which requires authentication. Until recently, you could only use your Telerik account credentials to authenticate with the Telerik NuGet server. However, a Telerik account that uses Google Authentication or custom SSO will notice no direct SSO login option to access the NuGet servers, and entering a username & password is a no-go. Luckily, the Progress Telerik team developed NuGet keys which can be used instead of the conventional username & password paradigm. >tip NuGet keys are helpful not only for Telerik users with Google Auth or SSO accounts but also for CI users and desktop developers. Learn more about the NuGet keys and how to use them by reading [this excellent blog post by Lance McCarthy](https://www.telerik.com/blogs/announcing-nuget-keys). -### Generating a NuGet Key +### Generating an API Key Generating a key for the Telerik NuGet server (https://nuget.telerik.com/v3/index.json) is fast and easy: -1. Open the [NuGet keys management page](https://www.telerik.com/account/downloads/nuget-keys). Alternatively, navigate to that page through **Account Overview** > **Downloads** > **Manage NuGet Keys** +1. Open the [API keys management page](https://www.telerik.com/account/downloads/api-keys). Alternatively, navigate to that page through **Account Overview** > **Downloads** > **API Keys** -1. Click the **Generate Key** button to create a new NuGet key. +1. Click the **Generate New Key** button to create a new NuGet key. 1. Copy and then store the value before replacing the contents of your clipboard. Note that this is the only time that you will see the key. Each generated key is valid for two years (or until explicitly deleted). ![Generate new key](./images/nuget-keys-telerik-001.png) -### Using the NuGet Key for Authentication +### Using the API Key for Authentication -Instead of entering a username and password through a Visual Studio prompt or a CLI command, the NuGet key must be provided through the NuGet.Config file. +Instead of entering a username and password through a Visual Studio prompt or a CLI command, the NuGet key must be provided through the `NuGet.Config` file. -You have the option to create a NuGet.Config file on the application level (it will overwrite any global NuGet.Config files and configuration will be applicable only for the specific application) or to use a global NuGet.Config file (it will be valid for all applications unless explicitly overwritten by an application NuGet.Config file). [Learn more details about NuGet.Config configuration and location on each operating system here...](https://learn.microsoft.com/en-us/nuget/consume-packages/configuring-nuget-behavior) +You have the option to create a `NuGet.Config` file on the application level (it will overwrite any global `NuGet.Config` files and configuration will be applicable only for the specific application) or to use a global `NuGet.Config` file (it will be valid for all applications unless explicitly overwritten by an application `NuGet.Config` file). [Learn more details about `NuGet.Config` configuration and location on each operating system here...](https://learn.microsoft.com/en-us/nuget/consume-packages/configuring-nuget-behavior) 1. Close all instances of Visual Studio. -1. Navigate to the directory where the NuGet.Config file resides. [Learn where is the location of NuGet.Config on each operating system here...](https://learn.microsoft.com/en-us/nuget/consume-packages/configuring-nuget-behavior#config-file-locations-and-uses) +1. Navigate to the directory where the `NuGet.Config` file resides. [Learn where is the location of `NuGet.Config` on each operating system here...](https://learn.microsoft.com/en-us/nuget/consume-packages/configuring-nuget-behavior#config-file-locations-and-uses) -1. Open the NuGet.Config file or create one if the file does not exist. +1. Open the `NuGet.Config` file or create one if the file does not exist. 1. Add the Telerik NuGet server in the package source section through a custom key (in the demo case, the key is named **MyTelerikFeed**) diff --git a/getting-started/telerik-nuget-server.md b/getting-started/telerik-nuget-server.md index c9e7ec0..2668292 100644 --- a/getting-started/telerik-nuget-server.md +++ b/getting-started/telerik-nuget-server.md @@ -9,31 +9,31 @@ position: 8 The following steps demonstrate how users can use the Telerik NuGet server to include our suite in their solution and/or update to the latest available version. -The credentials needed to access the Telerik NuGet server are the same as you use to log into your [Telerik account](https://www.telerik.com/account). The recommended approach to authenticate is to [generate]({%slug telerik-nuget-sso%}#generating-a-nuget-key) and [use]({%slug telerik-nuget-sso%}#using-the-nuget-key-for-authentication) the Telerik NuGet key. +The credentials needed to access the Telerik NuGet server are the same as you use to log into your [Telerik account](https://www.telerik.com/account). The recommended approach to authenticate is to [generate](slug://telerik-nuget-sso#generating-a-nuget-key) and [use](slug://telerik-nuget-sso#using-the-nuget-key-for-authentication) the Telerik NuGet key. ## Visual Studio The first step is to add the Telerik server to the NuGet package sources. This can be done in the Package Manager Settings from the Tools menu. -![](images/nuget-server/nuget-vs-pm-settings.png) +![](./images/nuget-server/nuget-vs-pm-settings.png) In the Package Sources section, users can add new sources. -![](images/nuget-server/nuget-vs-add-source.png) +![](./images/nuget-server/nuget-vs-add-source.png) In the Source field, users should fill in the address of the Telerik server (URL: **https://nuget.telerik.com/v3/index.json**) and click the Update button. >important The previous version of the Telerik NuGet server (https://nuget.telerik.com/nuget) will be deprecated. Update your settings to point to the new v3 API (URL: **https://nuget.telerik.com/v3/index.json**), which is faster, lighter, and reduces the number of requests from NuGet clients. -![](images/nuget-server/nuget-vs-telerik-server.png) +![](./images/nuget-server/nuget-vs-telerik-server.png) The Telerik server is now ready to use. Users can go to their solution and open the solution package manager. -![](images/nuget-server/nuget-vs-manage-packages.png) +![](./images/nuget-server/nuget-vs-manage-packages.png) Users have to find the **FiddlerCore** package and install it to their projects following these steps: -1. Select the Telerik server as a package source and enter their credentials when prompted. +1. Select the Telerik server as a package source. 1. Search for the FiddlerCore package. 1. Select the package when found. 1. Select which projects will have the package installed. @@ -41,11 +41,11 @@ Users have to find the **FiddlerCore** package and install it to their projects ![](images/nuget-server/nuget-vs-add-packages.png) ->tip You will need to autheticate when usiong the Telerik NuGet server. The recommended approach is to [generate and use a Telerik NuGet key]({%slug telerik-nuget-sso%}). +>tip You will need to autheticate when usiong the Telerik NuGet server. The recommended approach is to [generate and use a Telerik API key](slug://telerik-nuget-sso). ## Troubleshooting -#### Receiving 401 Logon failed Error +### Receiving 401 Logon failed Error If you're receiving this error when connecting to Telerik Nuget Server, you could try to update your NuGet credentials through the Windows Credential Manager. Please follow the steps below: @@ -53,11 +53,11 @@ If you're receiving this error when connecting to Telerik Nuget Server, you coul 1. Open the "Credential Manager" app on your PC; 1. Scroll through all the entries until you find any that are for nuget.telerik.com; 1. Once you find that entry, expand it and select "edit"; -1. Make sure the username and password are the same ones you use for your Telerik account (use the Email in the place of username) and click "Save". +1. Make sure you are using a valid API key. Now, you can reopen Visual Studio and access the Telerik NuGet server. ## Next Steps -- [Generate and use Telerik NuGet key instead of using credentials]({%slug telerik-nuget-sso%}) -- [FiddlerCore Configuration]({%slug configuration%}) +- [Generate and use Telerik NuGet key instead of using credentials](slug://telerik-nuget-sso) +- [FiddlerCore Configuration](slug://configuration) diff --git a/images/anchor.png b/images/anchor.png deleted file mode 100644 index 774cc96..0000000 Binary files a/images/anchor.png and /dev/null differ diff --git a/images/api.png b/images/api.png deleted file mode 100644 index 2c0acda..0000000 Binary files a/images/api.png and /dev/null differ diff --git a/images/arrow.png b/images/arrow.png deleted file mode 100644 index 9c5cce7..0000000 Binary files a/images/arrow.png and /dev/null differ diff --git a/images/caution-icon.png b/images/caution-icon.png deleted file mode 100644 index 4c23bb7..0000000 Binary files a/images/caution-icon.png and /dev/null differ diff --git a/images/close-btn.svg b/images/close-btn.svg deleted file mode 100644 index 69d57f2..0000000 --- a/images/close-btn.svg +++ /dev/null @@ -1,10 +0,0 @@ - - - - - - diff --git a/images/close.png b/images/close.png deleted file mode 100644 index 32968a7..0000000 Binary files a/images/close.png and /dev/null differ diff --git a/images/column.png b/images/column.png deleted file mode 100644 index 3115701..0000000 Binary files a/images/column.png and /dev/null differ diff --git a/images/common/avatar-ninja.svg b/images/common/avatar-ninja.svg new file mode 100644 index 0000000..4c88dee --- /dev/null +++ b/images/common/avatar-ninja.svg @@ -0,0 +1,77 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/images/common/no-results.svg b/images/common/no-results.svg new file mode 100644 index 0000000..9fe0515 --- /dev/null +++ b/images/common/no-results.svg @@ -0,0 +1,134 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/images/datagrid_localization.png b/images/datagrid_localization.png deleted file mode 100644 index 3260678..0000000 Binary files a/images/datagrid_localization.png and /dev/null differ diff --git a/images/datagrid_resourcemanager.png b/images/datagrid_resourcemanager.png deleted file mode 100644 index def5b10..0000000 Binary files a/images/datagrid_resourcemanager.png and /dev/null differ diff --git a/images/datagrid_resourcesfile.png b/images/datagrid_resourcesfile.png deleted file mode 100644 index 6ef772b..0000000 Binary files a/images/datagrid_resourcesfile.png and /dev/null differ diff --git a/images/external.png b/images/external.png deleted file mode 100644 index ac186fe..0000000 Binary files a/images/external.png and /dev/null differ diff --git a/images/file-white.png b/images/file-white.png deleted file mode 100644 index 7cf9916..0000000 Binary files a/images/file-white.png and /dev/null differ diff --git a/images/file.png b/images/file.png deleted file mode 100644 index bd47649..0000000 Binary files a/images/file.png and /dev/null differ diff --git a/images/folder-close.png b/images/folder-close.png deleted file mode 100644 index d3bea76..0000000 Binary files a/images/folder-close.png and /dev/null differ diff --git a/images/folder-open.png b/images/folder-open.png deleted file mode 100644 index 9b7691f..0000000 Binary files a/images/folder-open.png and /dev/null differ diff --git a/images/getting-started.png b/images/getting-started.png deleted file mode 100644 index 831ceef..0000000 Binary files a/images/getting-started.png and /dev/null differ diff --git a/images/howdoi.png b/images/howdoi.png deleted file mode 100644 index e066784..0000000 Binary files a/images/howdoi.png and /dev/null differ diff --git a/images/icon-telerik-badge.png b/images/icon-telerik-badge.png deleted file mode 100644 index 16b1403..0000000 Binary files a/images/icon-telerik-badge.png and /dev/null differ diff --git a/images/important-icon.png b/images/important-icon.png deleted file mode 100644 index 11838c6..0000000 Binary files a/images/important-icon.png and /dev/null differ diff --git a/images/important.png b/images/important.png deleted file mode 100644 index 2fcadf3..0000000 Binary files a/images/important.png and /dev/null differ diff --git a/images/logo.png b/images/logo.png deleted file mode 100644 index 13161a4..0000000 Binary files a/images/logo.png and /dev/null differ diff --git a/images/menu.png b/images/menu.png deleted file mode 100644 index 7dfa0da..0000000 Binary files a/images/menu.png and /dev/null differ diff --git a/images/minus.png b/images/minus.png deleted file mode 100644 index 921f244..0000000 Binary files a/images/minus.png and /dev/null differ diff --git a/images/nav-arrow.png b/images/nav-arrow.png deleted file mode 100644 index bc95c04..0000000 Binary files a/images/nav-arrow.png and /dev/null differ diff --git a/images/note-icon.png b/images/note-icon.png deleted file mode 100644 index 8572989..0000000 Binary files a/images/note-icon.png and /dev/null differ diff --git a/images/note-types/notetypes-actualappearance.png b/images/note-types/notetypes-actualappearance.png deleted file mode 100644 index 4b086c4..0000000 Binary files a/images/note-types/notetypes-actualappearance.png and /dev/null differ diff --git a/images/note-types/notetypes-mddeclaration.PNG b/images/note-types/notetypes-mddeclaration.PNG deleted file mode 100644 index acedd22..0000000 Binary files a/images/note-types/notetypes-mddeclaration.PNG and /dev/null differ diff --git a/images/open.png b/images/open.png deleted file mode 100644 index 2f9ba53..0000000 Binary files a/images/open.png and /dev/null differ diff --git a/images/plus.png b/images/plus.png deleted file mode 100644 index 097bb1d..0000000 Binary files a/images/plus.png and /dev/null differ diff --git a/images/search-24.png b/images/search-24.png deleted file mode 100644 index 7ffda8d..0000000 Binary files a/images/search-24.png and /dev/null differ diff --git a/images/search.png b/images/search.png deleted file mode 100644 index e88eb47..0000000 Binary files a/images/search.png and /dev/null differ diff --git a/images/tap-logo.png b/images/tap-logo.png deleted file mode 100644 index 50d893e..0000000 Binary files a/images/tap-logo.png and /dev/null differ diff --git a/images/tip-icon.png b/images/tip-icon.png deleted file mode 100644 index c2eebcc..0000000 Binary files a/images/tip-icon.png and /dev/null differ diff --git a/images/tutorials.png b/images/tutorials.png deleted file mode 100644 index d37dca3..0000000 Binary files a/images/tutorials.png and /dev/null differ diff --git a/introduction.md b/introduction.md index c6bc203..d20e8fb 100644 --- a/introduction.md +++ b/introduction.md @@ -14,7 +14,7 @@ Thank you for choosing Progress® Telerik® FiddlerCore! FiddlerCore is a .NET class library you can integrate into your .NET applications. It's available in .NET Standard 2.0, .NET Framework 4.0, and .NET Framework 4.5 flavors, which allows using it on Windows, Linux, Mac, and any other platform implementing .NET Standard. -FiddlerCore allows you to capture and modify HTTP and HTTPS traffic just like [Fiddler](https://www.telerik.com/fiddler), without any of the Fiddler UI. +FiddlerCore allows you to capture and modify HTTP and HTTPS traffic just like [Fiddler Everywhere](https://www.telerik.com/fiddler/fiddler-everywhere), without any of the Fiddler user interface. ## Features at a Glance @@ -26,4 +26,7 @@ FiddlerCore allows you to capture and modify HTTP and HTTPS traffic just like [F ## Next Steps -[First steps with FiddlerCore]({%slug first-steps%}) +[First steps with FiddlerCore](slug://first-steps) +[Using API Key to get FiddlerCore from Nuget](slug://telerik-nuget-sso) +[Basic FiddlerCore configuration](slug://configuration) +[Capturing HTTPS traffic with FiddlerCore](slug://capture-https-traffic) diff --git a/licensing/copyright.md b/licensing/copyright.md index 15c95ed..df172c6 100644 --- a/licensing/copyright.md +++ b/licensing/copyright.md @@ -10,7 +10,7 @@ position: 0 # Copyright -__© {{ site.time | date: '%Y' }} Progress Software Corporation and/or one of its subsidiaries or affiliates. All rights reserved.__ +Progress Software Corporation and/or one of its subsidiaries or affiliates. All rights reserved. These materials and all Progress® software products are copyrighted and all rights are reserved by Progress Software Corporation. The information in these materials is subject to change without notice, and Progress Software Corporation assumes no responsibility for any errors that may appear therein. The references in these materials to specific platforms supported are subject to change. diff --git a/release-history.md b/release-history.md index 20648c1..75f8b66 100644 --- a/release-history.md +++ b/release-history.md @@ -39,7 +39,7 @@ position: 300 #### Features -- Add x-`ConnectResponseRemoveConnectionClose` session flag (documented in the [Client flags]({%slug fiddler-core-session-flags%}#client-flags) section). +- Add x-`ConnectResponseRemoveConnectionClose` session flag (documented in the [Client flags](slug://fiddler-core-session-flags#client-flags) section). ## v5.0.0 FiddlerCore