ASP.NET

 $("#btnMultiJobChange").click(function (event) {        
        $.get("http://localhost:55429/BSCSecurityAddressBookWeb/MultiJobChange/", null, function (data) {
            //alert(data);
        });

public class MultiJobChangeController : Controller
{
    // GET: MultiJobChange
    public ActionResult Index()
    {
        return PartialView("~/Views/MultiJobChange/_Index.cshtml");
    }
}

<div id="target"></div>

<script>
    $(document).ready(function () {
        $.get("@Url.Action("Index", "MultiJobChange")", function (data) {
            $("#target").html(data);
        });
    });
</script>

$(document).ready(function () {
    $("#target").load("@Url.Action("Index", "MultiJobChange")");
});

window.location.href = '@Url.Action("Index", "MultiJobChange")';

public class MultiJobChangeController : Controller
{
    // GET: MultiJobChange
    public ActionResult Index()
    {
        return PartialView("~/Views/MultiJobChange/Index.cshtml");
    }
}

public class MultiJobChangeController : Controller
{
    // GET: MultiJobChange
    public ActionResult Index()
    {
        return PartialView("~/Views/MultiJobChange/_Index.cshtml");
    }
}

jkirkerx wrote:

I can't do a redirect because I have to action result as a return value

• Redirect[^];
• RedirectPermanent[^];
• RedirectToAction[^];
• RedirectToActionPermanent[^];

public ActionResult GetStarted(YourViewModel data)
{
    ...
    
    // Redirect to the "index" action on the "home" controller:
    return RedirectToAction("Index", "Home");
}

MVC FAQ – RickAndMSFT on Azure & MVC[^]:

The reason we don’t have a [RequireHttp] attribute in MVC is that there’s not really much benefit to it. It’s not as interesting as [RequireHttps], and it encourages users to do the wrong thing. For example, many web sites log in via SSL and redirect back to HTTP after you’re logged in, which is absolutely the wrong thing to do. Your login cookie is just as secret as your username + password, and now you’re sending it in cleartext across the wire. Besides, you’ve already taken the time to perform the handshake and secure the channel (which is the bulk of what makes HTTPS slower than HTTP) before the MVC pipeline is run, so [RequireHttp] won’t make the current request or future requests much faster.

[AttributeUsage(AttributeTargets.Class | AttributeTargets.Method, Inherited = true, AllowMultiple = false)]
public class RequireHttpAttribute : FilterAttribute, IAuthorizationFilter
{
    public virtual void OnAuthorization(AuthorizationContext filterContext)
    {
        if (filterContext == null) throw new ArgumentNullException(nameof(filterContext));

        if (filterContext.HttpContext.Request.IsSecureConnection)
        {
            HandleHttpsRequest(filterContext);
        }
    }

    protected virtual void HandleHttpsRequest(AuthorizationContext filterContext)
    {
        // only redirect for GET requests, otherwise the browser might not propagate the verb and request body correctly.

        if (!String.Equals(filterContext.HttpContext.Request.HttpMethod, "GET", StringComparison.OrdinalIgnoreCase))
        {
            throw new InvalidOperationException();
        }

        // redirect to HTTP version of page
        string url = "http://" + filterContext.HttpContext.Request.Url.Host + filterContext.HttpContext.Request.RawUrl;
        filterContext.Result = new RedirectResult(url);
    }
}