inteligr8/alfresco-community-repo
1
0
Fork 0
mirror of https://github.com/Alfresco/alfresco-community-repo.git synced 2025-07-24 17:32:48 +00:00
Code Issues Packages Projects Releases Wiki Activity

Made linkvalidation able to check HTTPS links with valid certs

Browse Source 
(bad/untrusted certs look like broken links), pretend ftp links 
aren't broken, detect old href schemas, and added low-level 
feature to drop href info on startup in case we ever need a 
sledgehammer.  Maybe one day I'll really validate ftp links, 
but not now.  Also fixed startup logic that got broken earlier
(the config file wasn't getting copied in).


git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/alfresco/HEAD/root@6183 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
This commit is contained in:
Jon Cox
2007-07-06 08:08:58 +00:00
parent 7d537bf42d
commit e1858011f8
1 changed files with 40 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

40
config/alfresco/linkvalidation-service-context.xml
View File

@@ -160,5 +160,45 @@
<property name="remoteConnectTimeout" value="10000"/> <property name="remoteConnectTimeout" value="10000"/>
<property name="localReadTimeout" value="30000"/> <property name="localReadTimeout" value="30000"/>
<property name="remoteReadTimeout" value="30000"/> <property name="remoteReadTimeout" value="30000"/>
<!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
<!-- Advanced Option: -->
<!-- -->
<!-- JSSE Security parameters (for validating HTTPS links) -->
<!-- -->
<!-- NOTE: -->
<!-- -->
<!-- When the following jsse properties below are commented -->
<!-- out the LinkValidationService uses the system's default -->
<!-- cacert file and password. Typically, there's no need to -->
<!-- change these values, but if you'd like to do so, you can. -->
<!-- -->
<!-- The most common case where you'd use a custom trust store -->
<!-- and password is when you want to validate https links for -->
<!-- which the name on the site's cert does not match the host -->
<!-- you're contacting, is invalid, and/or is not trusted. -->
<!-- If you do nothing, such links will appear "broken". -->
<!-- One option would be to modify your default cert at: -->
<!-- -->
<!-- Unix: ${JAVA_HOME}/lib/security/cacerts -->
<!-- Windows: ${JAVA_HOME}\lib\security\cacerts -->
<!-- -->
<!-- However, this is often not particularly desirable. -->
<!-- By allowing you to point at a custom cacert/password, -->
<!-- the configuration options below allow you to validate -->
<!-- what would be otherwise untrusted "broken" https links -->
<!-- without disturbing the system's default cacert file. -->
<!-- -->
<!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
<!-- <property name="jsseTrustStoreFile" value="...???..."/> -->
<!-- <property name="jsseTrustStorePassword" value="...???..."/> -->
<!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
<!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
<!-- Low-level parameters that typical users should never modify! -->
<!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
<property name="purgeAllValidationDataOnBootstrap" value="false"/>
</bean> </bean>
</beans> </beans>