[SERVER-12570] Specify allowed pages in various httpinterface modes Created: 31/Jan/14  Updated: 24/Feb/17  Resolved: 24/Feb/17

Status: Closed
Project: Core Server
Component/s: Admin
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Minor - P4
Reporter: Shaun Verch Assignee: DO NOT USE - Backlog - Platform Team
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-11707 mongos --jsonp is unusable without --... Closed
Participants:

 Description   

The httpinterface supports various pages, but there is no description of these pages and what modes (rest, jsonp, http) they are allowed in. This is a direct response to SERVER-11707.

Examples of pages that require rest:

http://localhost:28017/_commands
http://127.0.0.1:28017/databaseName/collectionName/

Examples of pages that do not require rest:

http://localhost:28017/_status
http://localhost:28017

This means that we see the following behavior when rest is not enabled:

These work:

http://localhost:28017/_status?jsonp=true
http://localhost:28017/_status

This does not work:

http://localhost:28017/?jsonp=true

Some pages that do not require rest can be used with jsonp even when rest is not enabled, but not all of them (see description for SERVER-11707). None of the pages that are linked from "localhost:28017" work without rest, which I think is part of the issue. I also don't see documentation for this "_status" page, so I don't know what the intended behavior is. There's actually a separate "serverStatus" page, which does require rest.


Generated at Thu Feb 08 03:28:54 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.