error_handlers page not show when deployed












0















I am new to google app engine, and want to host my php website on it. I found that there is a error_handlers option to redirect error(missing page) to custom error page, but when deployed, the error page never show.



I have try it with local server using dev_appserver.py app.yaml and it works. If I enter a file that is not exist, it will redirect to the error page. But when deployed to the web, it doesn't work.



This is my app.yaml. If the URL is not a php or html file, just simply redirect to index.php. But if it is a php or html file but not found, it will go to error.html.



runtime: php55
api_version: 1

handlers:
# Serve images as static resources.
- url: /(.+.(gif|png|jpg))$
static_files: 1
upload: .+.(gif|png|jpg)$
application_readable: true

# Serve php scripts.
- url: /(.+.(phphtml))$
script: 1

- url: /.*
script: index.php

error_handlers:
- file: error.html


In local server, it works fine and show the error page. When deployed, 404 error will appear for missing php or html. The error.html will never show, even if the URL is (domain).com/error.html. 404 error will show for error.html



I wonder if it is possible to redirect missing page to custom error page.










share|improve this question



























    0















    I am new to google app engine, and want to host my php website on it. I found that there is a error_handlers option to redirect error(missing page) to custom error page, but when deployed, the error page never show.



    I have try it with local server using dev_appserver.py app.yaml and it works. If I enter a file that is not exist, it will redirect to the error page. But when deployed to the web, it doesn't work.



    This is my app.yaml. If the URL is not a php or html file, just simply redirect to index.php. But if it is a php or html file but not found, it will go to error.html.



    runtime: php55
    api_version: 1

    handlers:
    # Serve images as static resources.
    - url: /(.+.(gif|png|jpg))$
    static_files: 1
    upload: .+.(gif|png|jpg)$
    application_readable: true

    # Serve php scripts.
    - url: /(.+.(phphtml))$
    script: 1

    - url: /.*
    script: index.php

    error_handlers:
    - file: error.html


    In local server, it works fine and show the error page. When deployed, 404 error will appear for missing php or html. The error.html will never show, even if the URL is (domain).com/error.html. 404 error will show for error.html



    I wonder if it is possible to redirect missing page to custom error page.










    share|improve this question

























      0












      0








      0


      0






      I am new to google app engine, and want to host my php website on it. I found that there is a error_handlers option to redirect error(missing page) to custom error page, but when deployed, the error page never show.



      I have try it with local server using dev_appserver.py app.yaml and it works. If I enter a file that is not exist, it will redirect to the error page. But when deployed to the web, it doesn't work.



      This is my app.yaml. If the URL is not a php or html file, just simply redirect to index.php. But if it is a php or html file but not found, it will go to error.html.



      runtime: php55
      api_version: 1

      handlers:
      # Serve images as static resources.
      - url: /(.+.(gif|png|jpg))$
      static_files: 1
      upload: .+.(gif|png|jpg)$
      application_readable: true

      # Serve php scripts.
      - url: /(.+.(phphtml))$
      script: 1

      - url: /.*
      script: index.php

      error_handlers:
      - file: error.html


      In local server, it works fine and show the error page. When deployed, 404 error will appear for missing php or html. The error.html will never show, even if the URL is (domain).com/error.html. 404 error will show for error.html



      I wonder if it is possible to redirect missing page to custom error page.










      share|improve this question














      I am new to google app engine, and want to host my php website on it. I found that there is a error_handlers option to redirect error(missing page) to custom error page, but when deployed, the error page never show.



      I have try it with local server using dev_appserver.py app.yaml and it works. If I enter a file that is not exist, it will redirect to the error page. But when deployed to the web, it doesn't work.



      This is my app.yaml. If the URL is not a php or html file, just simply redirect to index.php. But if it is a php or html file but not found, it will go to error.html.



      runtime: php55
      api_version: 1

      handlers:
      # Serve images as static resources.
      - url: /(.+.(gif|png|jpg))$
      static_files: 1
      upload: .+.(gif|png|jpg)$
      application_readable: true

      # Serve php scripts.
      - url: /(.+.(phphtml))$
      script: 1

      - url: /.*
      script: index.php

      error_handlers:
      - file: error.html


      In local server, it works fine and show the error page. When deployed, 404 error will appear for missing php or html. The error.html will never show, even if the URL is (domain).com/error.html. 404 error will show for error.html



      I wonder if it is possible to redirect missing page to custom error page.







      php google-app-engine error-handling google-cloud-platform app.yaml






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Dec 27 '18 at 14:28









      youmu_i19youmu_i19

      11




      11
























          1 Answer
          1






          active

          oldest

          votes


















          0














          In your app.yaml I think you are missing a in - url: /(.+.(phphtml))$ like this: /(.+.(php\html))$



          error_handlers only works for timeouts, over quota, and dos api denial errors.



          It seems to me that you are redirecting all your urls to index.php and creating the appropriated handler there for each url. In that case, you should catch the errors there with set_error_handler.



          For the 404, I will recommend the following:



          handlers:
          -url:/
          script: index.php

          -url:/*.
          script: 404_custom_error.php


          In this case, any url that can not be handled inside the index.php will then be handled by the 404 custom error php script, as shown in the app.yaml example.



          I found two public issue trackers discussing this topic. The first has info on a feature request and the second explains that the infrastructure will not intercept valid 404 responses.






          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',
            autoActivateHeartbeat: false,
            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%2f53946638%2ferror-handlers-page-not-show-when-deployed%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









            0














            In your app.yaml I think you are missing a in - url: /(.+.(phphtml))$ like this: /(.+.(php\html))$



            error_handlers only works for timeouts, over quota, and dos api denial errors.



            It seems to me that you are redirecting all your urls to index.php and creating the appropriated handler there for each url. In that case, you should catch the errors there with set_error_handler.



            For the 404, I will recommend the following:



            handlers:
            -url:/
            script: index.php

            -url:/*.
            script: 404_custom_error.php


            In this case, any url that can not be handled inside the index.php will then be handled by the 404 custom error php script, as shown in the app.yaml example.



            I found two public issue trackers discussing this topic. The first has info on a feature request and the second explains that the infrastructure will not intercept valid 404 responses.






            share|improve this answer






























              0














              In your app.yaml I think you are missing a in - url: /(.+.(phphtml))$ like this: /(.+.(php\html))$



              error_handlers only works for timeouts, over quota, and dos api denial errors.



              It seems to me that you are redirecting all your urls to index.php and creating the appropriated handler there for each url. In that case, you should catch the errors there with set_error_handler.



              For the 404, I will recommend the following:



              handlers:
              -url:/
              script: index.php

              -url:/*.
              script: 404_custom_error.php


              In this case, any url that can not be handled inside the index.php will then be handled by the 404 custom error php script, as shown in the app.yaml example.



              I found two public issue trackers discussing this topic. The first has info on a feature request and the second explains that the infrastructure will not intercept valid 404 responses.






              share|improve this answer




























                0












                0








                0







                In your app.yaml I think you are missing a in - url: /(.+.(phphtml))$ like this: /(.+.(php\html))$



                error_handlers only works for timeouts, over quota, and dos api denial errors.



                It seems to me that you are redirecting all your urls to index.php and creating the appropriated handler there for each url. In that case, you should catch the errors there with set_error_handler.



                For the 404, I will recommend the following:



                handlers:
                -url:/
                script: index.php

                -url:/*.
                script: 404_custom_error.php


                In this case, any url that can not be handled inside the index.php will then be handled by the 404 custom error php script, as shown in the app.yaml example.



                I found two public issue trackers discussing this topic. The first has info on a feature request and the second explains that the infrastructure will not intercept valid 404 responses.






                share|improve this answer















                In your app.yaml I think you are missing a in - url: /(.+.(phphtml))$ like this: /(.+.(php\html))$



                error_handlers only works for timeouts, over quota, and dos api denial errors.



                It seems to me that you are redirecting all your urls to index.php and creating the appropriated handler there for each url. In that case, you should catch the errors there with set_error_handler.



                For the 404, I will recommend the following:



                handlers:
                -url:/
                script: index.php

                -url:/*.
                script: 404_custom_error.php


                In this case, any url that can not be handled inside the index.php will then be handled by the 404 custom error php script, as shown in the app.yaml example.



                I found two public issue trackers discussing this topic. The first has info on a feature request and the second explains that the infrastructure will not intercept valid 404 responses.







                share|improve this answer














                share|improve this answer



                share|improve this answer








                edited Jan 2 at 15:35

























                answered Jan 2 at 15:21









                Nahuel VarelaNahuel Varela

                677214




                677214
































                    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.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53946638%2ferror-handlers-page-not-show-when-deployed%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

                    android studio warns about leanback feature tag usage required on manifest while using Unity exported app?

                    SQL update select statement

                    'app-layout' is not a known element: how to share Component with different Modules