![(please configure the [header_logo] section in trac.ini)](/trac/chrome/site/trac_banner.jpg)
Changeset 3663 in main for branches/2.1/src/main/webapps/ibisph-view/WEB-INF/web.xml
- Timestamp:
- 03/27/12 09:00:40 (10 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
branches/2.1/src/main/webapps/ibisph-view/WEB-INF/web.xml
r3636 r3663 50 50 <res-auth>Container</res-auth> 51 51 </resource-ref> 52 --> 52 53 <resource-ref> 53 54 <description>Resource reference to the app server container managed JNDI JavaMail factory</description> … … 57 58 <res-sharing-scope>Shareable</res-sharing-scope> 58 59 </resource-ref> 59 -->60 60 61 61 … … 130 130 131 131 <!-- ========================================= F I L T E R M A P P I N G S --> 132 <!-- These mappings are so that content can be zipped, headers modified 133 and other request/response filter manipulation. This is done with 134 Spring's delegating filter so that filters can have objects injected 135 and for the finer URL pattern matching that the delegating filter 136 provides. 132 <!-- The standard filters provide response compression (gzip), header 133 modifications for stuffing graphic types and cookie values, and to 134 handle other request/response manipulations. The security filters 135 provide authentication and authorization protection for the web URL/ 136 resource via Spring Security filters. Both types of filtering are 137 handled at a high level with Spring's delegating filter. Spring's 138 delegating proxy filter provides 2 important capabilities not found in 139 standard web.xml filter mappings: 1) more flexible URL to filter 140 mappings, and 2) the ability to configure filters using spring 141 injection. Each filter definition has the detailed filter mappings 142 which makes this web.xml simplier and allows the filters to all be 143 contained in one area and easier to maintain. 137 144 --> 138 145 <filter-mapping> 139 146 <filter-name>StandardFilters</filter-name> 140 <url-pattern>/home/*</url-pattern> 141 </filter-mapping> 142 <filter-mapping> 143 <filter-name>StandardFilters</filter-name> 144 <url-pattern>/publications/*</url-pattern> 145 </filter-mapping> 146 <filter-mapping> 147 <filter-name>StandardFilters</filter-name> 148 <url-pattern>/indicator/*</url-pattern> 149 </filter-mapping> 150 <filter-mapping> 151 <filter-name>StandardFilters</filter-name> 152 <url-pattern>/query/*</url-pattern> 153 </filter-mapping> 154 <filter-mapping> 155 <filter-name>StandardFilters</filter-name> 156 <url-pattern>/secure/*</url-pattern> 157 </filter-mapping> 158 <filter-mapping> 159 <filter-name>StandardFilters</filter-name> 160 <url-pattern>/phom/*</url-pattern> 161 </filter-mapping> 162 <filter-mapping> 163 <filter-name>StandardFilters</filter-name> 164 <url-pattern>/community/*</url-pattern> 165 </filter-mapping> 166 167 <filter-mapping> 168 <filter-name>StandardFilters</filter-name> 169 <url-pattern>/css/*</url-pattern> 170 </filter-mapping> 171 <filter-mapping> 172 <filter-name>StandardFilters</filter-name> 173 <url-pattern>/image/*</url-pattern> 174 </filter-mapping> 175 <filter-mapping> 176 <filter-name>StandardFilters</filter-name> 177 <url-pattern>/js/*</url-pattern> 178 </filter-mapping> 179 180 <filter-mapping> 181 <filter-name>SecurityFilters</filter-name> 182 <url-pattern>/user/*</url-pattern> 147 <url-pattern>*</url-pattern> 183 148 </filter-mapping> 184 149 <filter-mapping> 185 150 <filter-name>SecurityFilters</filter-name> 186 <url-pattern>/query/definition/*</url-pattern> 187 </filter-mapping> 188 <filter-mapping> 189 <filter-name>SecurityFilters</filter-name> 190 <url-pattern>/query/criteria/*</url-pattern> 191 </filter-mapping> 192 193 <filter-mapping> 194 <filter-name>SecurityFilters</filter-name> 195 <url-pattern>/secure/*</url-pattern> 196 </filter-mapping> 197 198 <!-- 199 Entries needed to check that publish requests are originating from a 200 specified IP address. The address is specified either in the spring 201 bean config file or in a property file and should be set to the IP 202 address of the computer that the admin app lives on. If the direct XML 203 file publishing or a bundled deployment mechanism is used then these 204 are not needed - but do no harm in being left as a default configuration 205 - the URLs are simply never hit. 206 --> 207 <filter-mapping> 208 <filter-name>SecurityFilters</filter-name> 209 <url-pattern>/publish/*</url-pattern> 210 </filter-mapping> 211 <filter-mapping> 212 <filter-name>SecurityFilters</filter-name> 213 <url-pattern>/unpublish/*</url-pattern> 151 <url-pattern>*</url-pattern> 214 152 </filter-mapping> 215 153 … … 246 184 247 185 <!-- ======================================= S E R V L E T M A P P I N G S --> 248 <!-- 249 NOTE: need to map each system and NOT have a general /* mapping because 250 the servlet will then receive requests for image files, js, css etc... 186 <!-- Servlet and filter URL mappings have the same exact limitations as 187 such they are handled in a similar manner - all requests are routed 188 to the Spring request dispaatcher servlet which uses more robust URL 189 to controller mappings. This is not very efficient for static content 190 but static content has header values that encourage the browser to cache 191 its content. 192 193 setup the dispatcher servlet to handle all requsets with the defaul explicitly 194 configed to handle all static content: 195 <servlet-mapping> 196 <servlet-name>default</servlet-name> 197 <url-pattern>/css/*</url-pattern> 198 <url-pattern>/image/*</url-pattern> 199 <url-pattern>*.ico</url-pattern> 200 <url-pattern>/js/*</url-pattern> 201 <url-pattern>*.jsp</url-pattern> 202 <url-pattern>/xml/*</url-pattern> 203 </servlet-mapping> 204 205 <url-pattern>/*</url-pattern> 206 207 the above has an issue with the path prefix needing to be stripped for 208 the correct xml file path. Doing this would however do away with the 209 ds needing to check full path and the below mappings which are basically 210 used to strip url path prefixes. 251 211 --> 252 212 <servlet-mapping> 253 213 <servlet-name>Dispatcher.Servlet</servlet-name> 214 254 215 <url-pattern>/home/*</url-pattern> 255 </servlet-mapping>256 <servlet-mapping>257 <servlet-name>Dispatcher.Servlet</servlet-name>258 216 <url-pattern>/publications/*</url-pattern> 259 </servlet-mapping>260 <servlet-mapping>261 <servlet-name>Dispatcher.Servlet</servlet-name>262 217 <url-pattern>/indicator/*</url-pattern> 263 </servlet-mapping>264 <servlet-mapping>265 <servlet-name>Dispatcher.Servlet</servlet-name>266 218 <url-pattern>/community/*</url-pattern> 267 </servlet-mapping>268 <servlet-mapping>269 <servlet-name>Dispatcher.Servlet</servlet-name>270 219 <url-pattern>/query/*</url-pattern> 271 </servlet-mapping>272 <servlet-mapping>273 <servlet-name>Dispatcher.Servlet</servlet-name>274 220 <url-pattern>/user/*</url-pattern> 275 </servlet-mapping>276 <servlet-mapping>277 <servlet-name>Dispatcher.Servlet</servlet-name>278 221 <url-pattern>/secure/*</url-pattern> 279 </servlet-mapping>280 <servlet-mapping>281 <servlet-name>Dispatcher.Servlet</servlet-name>282 222 <url-pattern>/phom/*</url-pattern> 283 </servlet-mapping> 284 285 <!-- generic transformation request handler --> 286 <servlet-mapping> 287 <servlet-name>Dispatcher.Servlet</servlet-name> 223 288 224 <url-pattern>/view/*</url-pattern> 225 <url-pattern>/edit/*</url-pattern> 226 <url-pattern>/save/*</url-pattern> 227 <url-pattern>/delete/*</url-pattern> 228 <url-pattern>/run/*</url-pattern> 229 <url-pattern>/apply/*</url-pattern> 230 <url-pattern>/send/*</url-pattern> 231 232 <!-- 233 Default publishing URL mapping that even if direct publishing is 234 configured in the admin app does no harm as these URLs are never hit. 235 --> 236 <url-pattern>/publish/*</url-pattern> 237 <url-pattern>/unpublish/*</url-pattern> 289 238 </servlet-mapping> 290 239 … … 301 250 <servlet-mapping> 302 251 <servlet-name>Dispatcher.Servlet</servlet-name> 252 303 253 <url-pattern>/indicator/graphic/*</url-pattern> 304 </servlet-mapping>305 <servlet-mapping>306 <servlet-name>Dispatcher.Servlet</servlet-name>307 254 <url-pattern>/query/selection/*</url-pattern> 308 </servlet-mapping>309 <servlet-mapping>310 <servlet-name>Dispatcher.Servlet</servlet-name>311 255 <url-pattern>/query/configuration/*</url-pattern> 312 </servlet-mapping>313 <servlet-mapping>314 <servlet-name>Dispatcher.Servlet</servlet-name>315 256 <url-pattern>/query/builder/*</url-pattern> 316 </servlet-mapping>317 <servlet-mapping>318 <servlet-name>Dispatcher.Servlet</servlet-name>319 257 <url-pattern>/query/submit/*</url-pattern> 320 </servlet-mapping>321 <servlet-mapping>322 <servlet-name>Dispatcher.Servlet</servlet-name>323 258 <url-pattern>/query/result/*</url-pattern> 324 </servlet-mapping>325 <servlet-mapping>326 <servlet-name>Dispatcher.Servlet</servlet-name>327 259 <url-pattern>/query/result/graphic/*</url-pattern> 328 </servlet-mapping> 329 330 <servlet-mapping> 331 <servlet-name>Dispatcher.Servlet</servlet-name> 260 332 261 <url-pattern>/secure/query/selection/*</url-pattern> 333 </servlet-mapping>334 <servlet-mapping>335 <servlet-name>Dispatcher.Servlet</servlet-name>336 262 <url-pattern>/secure/query/configuration/*</url-pattern> 337 </servlet-mapping>338 <servlet-mapping>339 <servlet-name>Dispatcher.Servlet</servlet-name>340 263 <url-pattern>/secure/query/builder/*</url-pattern> 341 </servlet-mapping>342 <servlet-mapping>343 <servlet-name>Dispatcher.Servlet</servlet-name>344 264 <url-pattern>/secure/query/submit/*</url-pattern> 345 </servlet-mapping>346 <servlet-mapping>347 <servlet-name>Dispatcher.Servlet</servlet-name>348 265 <url-pattern>/secure/query/result/*</url-pattern> 349 </servlet-mapping>350 <servlet-mapping>351 <servlet-name>Dispatcher.Servlet</servlet-name>352 266 <url-pattern>/secure/query/result/graphic/*</url-pattern> 353 267 </servlet-mapping> 354 268 355 <!--356 Default publishing URL mapping that even if direct publishing is357 configured in the admin app does no harm as these URLs are never hit.358 -->359 <servlet-mapping>360 <servlet-name>Dispatcher.Servlet</servlet-name>361 <url-pattern>/publish/*</url-pattern>362 </servlet-mapping>363 <servlet-mapping>364 <servlet-name>Dispatcher.Servlet</servlet-name>365 <url-pattern>/unpublish/*</url-pattern>366 </servlet-mapping>367 368 <servlet-mapping>369 <servlet-name>Dispatcher.Servlet</servlet-name>370 <url-pattern>/Welcome</url-pattern>371 </servlet-mapping>372 373 <!-- Blocked direct file access URLs. Files that need to be blocked from374 public access can have a general mapping that goes to a simple controller375 that returns a missing resource page. This could also be mapped to a376 general controller that simply returns a 404 or 403 error. Remember that377 a corresponding mapping needs to exist in the dispatcher_servlet.xml378 file as well as here in the servlet mapping. There are other ways to379 impelment like putting the files within a WEB-INF/* subdirectory. Can380 also be done via a filter (like the CheckAllowedRequesterIPAddressFilter)381 or via a similar filter etc.382 -->383 <servlet-mapping>384 <servlet-name>Dispatcher.Servlet</servlet-name>385 <url-pattern>/xml/users/*</url-pattern>386 </servlet-mapping>387 269 388 270 … … 494 376 <!-- =============================== D E F A U L T / W E L C O M E P A G E --> 495 377 <welcome-file-list> 496 <welcome-file> Welcome</welcome-file>378 <welcome-file>home/Welcome.html</welcome-file> 497 379 </welcome-file-list> 498 380
Note: See TracChangeset
for help on using the changeset viewer.
