Search Tips

U.S. Supreme Court accepts new Oklahoma case about Indian reservations Monday, December 16, 2019

The Oklahoman

The U.S. Supreme Court, which failed this year to decide a case that could have a major impact in eastern Oklahoma, has chosen a different path to determine whether tribal reservations in the state were officially terminated.

The high court agreed Friday to review the appeal of a man convicted of child sex crimes who contends he should not have been tried in an Oklahoma state court. Jimcy McGirt told the court the Muscogee (Creek) Nation has jurisdiction over his case since he is a member of the tribe and the offenses were committed on land that is still part of the tribe’s reservation.

According to written arguments filed in McGirt’s case by the Oklahoma attorney general’s office, the question presented by McGirt is “identical” to the one that the Supreme Court could not resolve this year.

Read more at: https://oklahoman.com/article/5649909/us-supreme-court-accepts-new-oklahoma-case-about-indian-reservations

 

Runtime Error

Server Error in '/' Application.

Runtime Error

Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".


<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="Off"/>
    </system.web>
</configuration>

Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.


<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
    </system.web>
</configuration>