Abstract

The article presents the main provisions of the construction of web applications. The mechanism of the application protocol HTTP in the development of web applications. The description of the operation of HTTP status codes and their processing in the user’s browser is given. Describes how to use status codes in the development of web applications. An example of working with a redirection code and header is given. A definition and characterization of execution vulnerabilities after redirection is proposed. Examples of applications vulnerable to run after redirection to server programming languages PHP and Ruby on Rails are given. Describes the problem of typical solutions to neutralize the vulnerability of execution after redirection. A way of writing the source code of the application, taking into account the possibility of execution vulnerabilities after redirection, is proposed. Provides recommendations for writing code.

Highlights

  • Введение На фоне роста количества веб-ресурсов растет и количество угроз их безопасности

  • Для ее понимания необходимы хо‐ рошие знания функционирования Интернета и сети в целом

  • Examples of applications vulnerable to run after redirection to server programming languages PHP and Ruby on Rails are given

Read more

Summary

Introduction

Введение На фоне роста количества веб-ресурсов растет и количество угроз их безопасности. В заголовок обычно выносится сервисная информация, не нужная большинству пользовате‐ лей, а в теле обычно содержится сам исходный код веб-страниц, которые пользователь видит в своем браузере. Для этих целей в протоколе HTTP было введено понятие кода ответа. Обычно подразу‐ мевается, что исполнение кода на стороне сервера заканчивается перенаправлением, так как в брау‐ зере уже отображается другая страница [3].

Results
Conclusion
Full Text
Paper version not known

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.