You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@sling.apache.org by ro...@apache.org on 2017/03/23 09:32:31 UTC
svn commit: r1788211 -
/sling/site/trunk/content/documentation/the-sling-engine/servlets.mdtext
Author: rombert
Date: Thu Mar 23 09:32:31 2017
New Revision: 1788211
URL: http://svn.apache.org/viewvc?rev=1788211&view=rev
Log:
SLING-6699 - Clearly describe drawbacks of mounting servlets by path
Typo fix
Modified:
sling/site/trunk/content/documentation/the-sling-engine/servlets.mdtext
Modified: sling/site/trunk/content/documentation/the-sling-engine/servlets.mdtext
URL: http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/the-sling-engine/servlets.mdtext?rev=1788211&r1=1788210&r2=1788211&view=diff
==============================================================================
--- sling/site/trunk/content/documentation/the-sling-engine/servlets.mdtext (original)
+++ sling/site/trunk/content/documentation/the-sling-engine/servlets.mdtext Thu Mar 23 09:32:31 2017
@@ -26,7 +26,7 @@ Each path to be used for registration -
If `sling.servlet.methods` is not specified, the servlet is only registered for handling GET and HEAD requests. Make sure to list all methods you want to be handled by this servlet.
-### Caveats when binding servlets by paths
+### Caveats when binding servlets by path
Binding servlets by paths has several disadvantages when compared to binding by resource types, namely: