Forward requests from example.com:8000 (old REST API) to api.example.com (new REST API) on AWS











up vote
0
down vote

favorite












So I have this problem and I am a bit confused on where to start. I have a Django REST API currently running on a VPS (with apache) and start with djangos runserver command (I know, I know, not the best way) so it is currently accessed via http://example.com:8000/api.



I am now moving to AWS and using Elastic Beanstalk to run my newly created Django REST API. I want to keep the domain something like example.com/api or api.example.com. Now this should be fine for me to set up but the problem I now have is I want to forward all old requests using the old API to the new API. What is the best way to do this?



Any help will be appreciated! :)






amazon-web-services amazon-s3 amazon-ec2 amazon-route53 amazon-elastic-beanstalk







share|improve this question






















  • It's important to know that if your API uses POST then it may or may not be properly supported with a redirect. See here for many more details.
    – stdunbar
    Nov 12 at 0:03















up vote
0
down vote

favorite












So I have this problem and I am a bit confused on where to start. I have a Django REST API currently running on a VPS (with apache) and start with djangos runserver command (I know, I know, not the best way) so it is currently accessed via http://example.com:8000/api.



I am now moving to AWS and using Elastic Beanstalk to run my newly created Django REST API. I want to keep the domain something like example.com/api or api.example.com. Now this should be fine for me to set up but the problem I now have is I want to forward all old requests using the old API to the new API. What is the best way to do this?



Any help will be appreciated! :)






amazon-web-services amazon-s3 amazon-ec2 amazon-route53 amazon-elastic-beanstalk







share|improve this question






















  • It's important to know that if your API uses POST then it may or may not be properly supported with a redirect. See here for many more details.
    – stdunbar
    Nov 12 at 0:03













up vote
0
down vote

favorite









up vote
0
down vote

favorite











So I have this problem and I am a bit confused on where to start. I have a Django REST API currently running on a VPS (with apache) and start with djangos runserver command (I know, I know, not the best way) so it is currently accessed via http://example.com:8000/api.



I am now moving to AWS and using Elastic Beanstalk to run my newly created Django REST API. I want to keep the domain something like example.com/api or api.example.com. Now this should be fine for me to set up but the problem I now have is I want to forward all old requests using the old API to the new API. What is the best way to do this?



Any help will be appreciated! :)






amazon-web-services amazon-s3 amazon-ec2 amazon-route53 amazon-elastic-beanstalk







share|improve this question













So I have this problem and I am a bit confused on where to start. I have a Django REST API currently running on a VPS (with apache) and start with djangos runserver command (I know, I know, not the best way) so it is currently accessed via http://example.com:8000/api.



I am now moving to AWS and using Elastic Beanstalk to run my newly created Django REST API. I want to keep the domain something like example.com/api or api.example.com. Now this should be fine for me to set up but the problem I now have is I want to forward all old requests using the old API to the new API. What is the best way to do this?



Any help will be appreciated! :)






amazon-web-services amazon-s3 amazon-ec2 amazon-route53 amazon-elastic-beanstalk




amazon-web-services amazon-s3 amazon-ec2 amazon-route53 amazon-elastic-beanstalk






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 11 at 17:06









Jokas Lokas

891110




891110












  • It's important to know that if your API uses POST then it may or may not be properly supported with a redirect. See here for many more details.
    – stdunbar
    Nov 12 at 0:03


















  • It's important to know that if your API uses POST then it may or may not be properly supported with a redirect. See here for many more details.
    – stdunbar
    Nov 12 at 0:03
















It's important to know that if your API uses POST then it may or may not be properly supported with a redirect. See here for many more details.
– stdunbar
Nov 12 at 0:03




It's important to know that if your API uses POST then it may or may not be properly supported with a redirect. See here for many more details.
– stdunbar
Nov 12 at 0:03












1 Answer
1






active

oldest

votes

















up vote
0
down vote













There are two ways to do this.




  • Rewrite

  • Redirect


Rewrite:



With rewrite you read the contents using the old api and serve on the same request.



Redirect:



With redirect you send a 302 with the redirect location to your new API url.



Any request to http://example.com:8000/api/something will be responded with a http status code 302 and location as http://example.com/api/something or http://api.example.com/something



If you do not wish you to use the old API, then it is better to redirect to the new destination.



If changing the URL on the client side is possible, then you can abondon mantaining the old endpoint or any of these process.



Hope it helps.






share|improve this answer





















    Your Answer






    StackExchange.ifUsing("editor", function () {
    StackExchange.using("externalEditor", function () {
    StackExchange.using("snippets", function () {
    StackExchange.snippets.init();
    });
    });
    }, "code-snippets");

    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "1"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53251127%2fforward-requests-from-example-com8000-old-rest-api-to-api-example-com-new-re%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes








    up vote
    0
    down vote













    There are two ways to do this.




    • Rewrite

    • Redirect


    Rewrite:



    With rewrite you read the contents using the old api and serve on the same request.



    Redirect:



    With redirect you send a 302 with the redirect location to your new API url.



    Any request to http://example.com:8000/api/something will be responded with a http status code 302 and location as http://example.com/api/something or http://api.example.com/something



    If you do not wish you to use the old API, then it is better to redirect to the new destination.



    If changing the URL on the client side is possible, then you can abondon mantaining the old endpoint or any of these process.



    Hope it helps.






    share|improve this answer

























      up vote
      0
      down vote













      There are two ways to do this.




      • Rewrite

      • Redirect


      Rewrite:



      With rewrite you read the contents using the old api and serve on the same request.



      Redirect:



      With redirect you send a 302 with the redirect location to your new API url.



      Any request to http://example.com:8000/api/something will be responded with a http status code 302 and location as http://example.com/api/something or http://api.example.com/something



      If you do not wish you to use the old API, then it is better to redirect to the new destination.



      If changing the URL on the client side is possible, then you can abondon mantaining the old endpoint or any of these process.



      Hope it helps.






      share|improve this answer























        up vote
        0
        down vote










        up vote
        0
        down vote









        There are two ways to do this.




        • Rewrite

        • Redirect


        Rewrite:



        With rewrite you read the contents using the old api and serve on the same request.



        Redirect:



        With redirect you send a 302 with the redirect location to your new API url.



        Any request to http://example.com:8000/api/something will be responded with a http status code 302 and location as http://example.com/api/something or http://api.example.com/something



        If you do not wish you to use the old API, then it is better to redirect to the new destination.



        If changing the URL on the client side is possible, then you can abondon mantaining the old endpoint or any of these process.



        Hope it helps.






        share|improve this answer












        There are two ways to do this.




        • Rewrite

        • Redirect


        Rewrite:



        With rewrite you read the contents using the old api and serve on the same request.



        Redirect:



        With redirect you send a 302 with the redirect location to your new API url.



        Any request to http://example.com:8000/api/something will be responded with a http status code 302 and location as http://example.com/api/something or http://api.example.com/something



        If you do not wish you to use the old API, then it is better to redirect to the new destination.



        If changing the URL on the client side is possible, then you can abondon mantaining the old endpoint or any of these process.



        Hope it helps.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Nov 11 at 19:54









        Kannaiyan

        5,87611942




        5,87611942






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Stack Overflow!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid …



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.





            Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


            Please pay close attention to the following guidance:


            • Please be sure to answer the question. Provide details and share your research!

            But avoid …



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53251127%2fforward-requests-from-example-com8000-old-rest-api-to-api-example-com-new-re%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            -

            Popular posts from this blog

            Florida Star v. B. J. F.

            Image
            Florida Star v. B. J. F. From Wikipedia, the free encyclopedia Jump to navigation Jump to search United States Supreme Court case Florida Star v. B. J. F. Supreme Court of the United States Argued March 21, 1989 Decided June 21, 1989 Full case name The Florida Star v. B. J. F. Citations 491 U.S. 524 ( more ) 109 S. Ct. 2603; 105 L. Ed. 2d 443; 1989 U.S. LEXIS 3120; 57 U.S.L.W. 4816; 16 Media L. Rep. 1801 Prior history The Florida Star v. B.J.F., 530 So.2d 286 (1988) Supreme Court of Florida; Florida Star v. B.J.F., 499 So.2d 883 (1986) Fla. Dist. Court of Appeals Holding Florida Stat. § 794.03 is unconstitutional to the extent it makes the truthful reporting of information that was a matter of public record unlawful, as it violates the First Amendment. Court membership Chief Justice William Rehnquist Associate Justices William J. Brennan Jr.  · Byron White Thurgood Marshall  · Harry Blac
            Read more

            Error while running script in elastic search , gateway timeout

            Image
            0 while running script in elastic search, I got 504 Gateway timeout error. { "query": { "bool": { "filter": { "script": { "script": " doc['creted_date'].date.getMonthOfYear() == 12 " } } } }, "aggs": { "test": { "date_histogram": { "field": "creted_date", "interval": "month", "format": "MMM" }, "aggs": { "cost": { "sum": { "field": "cost" } } }
            Read more

            Adding quotations to stringified JSON object values

            Image
            0 My stringified object data doesn't include quotation marks around object values, which errors when attempting JSON.parse() : '{ "affiliation": CORPORATE, "userId": 75c35d1c-5d12-4485-8fa8-b2f1551a3e6e }' I need the string to be: '{ "affiliation": "CORPORATE", "userId": "75c35d1c-5d12-4485-8fa8-b2f1551a3e6e" }' I'm using this regex to add quotes to the object keys: var newStr = str.replace(/(['"])?([a-z0-9A-Z_]+)(['"])?:/g, '"$2": '); For instance: '{ affiliation: CORPORATE }' to '{ "affiliation": CORPORATE }' There are only string values in my data, so I don't need to check value types. How can I alter my regex expression to add quotations to
            Read more