Differences

This shows you the differences between the selected revisions of the page.

2013-11-15 2013-12-20
win_vista_and_newer anchor (martin) 5.5 removing beta tags (martin)
Line 9: Line 9:
==== [[win_vista_and_newer]] Windows Vista and Newer ==== ==== [[win_vista_and_newer]] Windows Vista and Newer ====
On Windows Vista, 7 and 8, WinSCP registers to list of applications that handle ''%%sftp://%%'', ''%%ftp://%%'', ''%%ftps://%%'' and ''%%scp://%%'' protocol URL addresses. &winvista &win7 &win8 If WinSCP is the first application to support some of these protocols (most often ''%%sftp://%%'' and ''%%scp://%%'', usually also ''%%ftps://%%''), it becomes a default application for these. On Windows Vista, 7 and 8, WinSCP registers to list of applications that handle ''%%sftp://%%'', ''%%ftp://%%'', ''%%ftps://%%'' and ''%%scp://%%'' protocol URL addresses. &winvista &win7 &win8 If WinSCP is the first application to support some of these protocols (most often ''%%sftp://%%'' and ''%%scp://%%'', usually also ''%%ftps://%%''), it becomes a default application for these.
- 
-&beta_feature //In previous releases WinSCP behaves as described in [[integration_url#winxp|Windows XP section]]//. 
If you want to change the registration (for instance to make WinSCP default application even for ''%%ftp://%%'' URL addresses): If you want to change the registration (for instance to make WinSCP default application even for ''%%ftp://%%'' URL addresses):
Line 32: Line 30:
==== [[winscp]] WinSCP-specific URL protocols ==== ==== [[winscp]] WinSCP-specific URL protocols ====
In addition to registering to generic URL protocols, WinSCP registers for application-specific URL protocols with ''winscp-'' prefix, i.e. ''%%winscp-sftp://%%'', ''%%winscp-ftp://%%'', etc. This is particularly useful for FTP protocol, for which WinSCP competes with your default web browser. Also for links on web pages, web browsers typically ignore system registration for ''%%ftp://%%'' addresses and handle these on their own anyway. In addition to registering to generic URL protocols, WinSCP registers for application-specific URL protocols with ''winscp-'' prefix, i.e. ''%%winscp-sftp://%%'', ''%%winscp-ftp://%%'', etc. This is particularly useful for FTP protocol, for which WinSCP competes with your default web browser. Also for links on web pages, web browsers typically ignore system registration for ''%%ftp://%%'' addresses and handle these on their own anyway.
- 
-&beta_feature 
Using WinSCP-specific URL protocols is reasonable also, when using WinSCP-specific extension for URL syntax, particularly the [[integration_url#save|save extension]]. Using WinSCP-specific URL protocols is reasonable also, when using WinSCP-specific extension for URL syntax, particularly the [[integration_url#save|save extension]].
Line 46: Line 42:
To make WinSCP [[session_configuration#site|save session settings]] provided by URL to a site instead of opening a session, add '';save'' after a path part of the URL (it there is no path part, terminate the URL with ''/'' before adding the '';save'' extension). To make WinSCP [[session_configuration#site|save session settings]] provided by URL to a site instead of opening a session, add '';save'' after a path part of the URL (it there is no path part, terminate the URL with ''/'' before adding the '';save'' extension).
- 
-&beta_feature 
For SFTP/SCP URL this should be combined with including [[session_url#hostkey|SSH host key fingerprint in the URL]]. As this is WinSCP-specific extension, and also to avoid conflicts with other applications, like web browsers, consider using [[integration_url#winscp|WinSCP-specific URL protocols]]. For SFTP/SCP URL this should be combined with including [[session_url#hostkey|SSH host key fingerprint in the URL]]. As this is WinSCP-specific extension, and also to avoid conflicts with other applications, like web browsers, consider using [[integration_url#winscp|WinSCP-specific URL protocols]].

Last modified: by martin