Restricting Administrative Non-Map Requests

1-28 Oracle Fusion Middleware Users Guide for Oracle MapViewer this case should be ....images, because the physical images directory is mapviewer.earweb.warimages; so using relative path, the value should be ....images for the path attribute to resolve to the physical directory. ■ The life attribute specifies the number of minutes that a generated map image is guaranteed to stay on the file system before the image is deleted. If the life attribute is specified, the recycle_interval attribute controls how frequently MapViewer checks for possible files to delete. Default: MapViewer never deletes the generated map images. ■ The recycle_interval attribute specifies the number of minutes between times when MapViewer checks to see if it can delete any image files that have been on the file system longer than the number of minutes for the life attribute value. Default value: 480 8 hours

1.5.2.3 Restricting Administrative Non-Map Requests

In addition to map requests, MapViewer accepts administrative non-map requests, such as requests to list all data sources and to add and delete data sources. Chapter 7 describes the administrative requests. By default, all MapViewer users are permitted to make administrative requests. However, if you want to restrict the ability to submit administrative requests, you can edit the MapViewer configuration file to allow administrative requests only from users with specified IP addresses. To restrict administrative requests to users at specified IP addresses, add the ip_ monitor element to the MapViewer configuration file or uncomment and modify an existing element, if one is commented out. Example 1–2 shows a sample ip_ monitor element excerpt from a configuration file. Example 1–2 Restricting Administrative Requests MapperConfig . . . ip_monitor ips 138.1.17.9, 138.1.17.21, 138.3., 20. ips ip_range 24.17.1.3 - 24.17.1.20 ip_range ips_exclude 138.3.29. ips_exclude ip_range_exclude20.22.34.1 - 20.22.34.255ip_range_exclude ip_monitor . . . MapperConfig In Example 1–2 : ■ The following IP addresses are explicitly included as able to submit administrative requests unless excluded by an ips_exclude element: 138.1.17.9, 138.1.17.21, all that start with 138.3., all that start with 20., and all in the range inclusive of 24.17.1.3 to 24.17.1.20. ■ The following IP addresses are explicitly excluded from submitting administrative requests: all starting with 138.3.29., and all in the range inclusive of 20.22.34.1 to 20.22.34.255. ■ All other IP addresses that are not explicitly included cannot submit administrative requests. Syntax notes for the ip_monitor element: Introduction to MapViewer 1-29 ■ Use ips and ip_range elements to specify which IP addresses and ranges are allowed. Asterisk wildcards such as 20. are acceptable. Use a comma-delimited list for addresses. ■ Use ips_exclude and ip_range_exclude elements to exclude IP addresses and address ranges from submitting administrative requests. If an address falls into both the included and excluded category, it is excluded. ■ If you specify the asterisk wildcard in an ips element, all associated IP addresses are included except any specified in ips_exclude and ip_ range_exclude elements.

1.5.2.4 Specifying a Web Proxy