[JIRA] (JENKINS-59181) The plain HTTP request was sent to HTTPS port

8 views
Skip to first unread message

eugene.pliskin@gmail.com (JIRA)

unread,
Sep 2, 2019, 7:00:02 AM9/2/19
to jenkinsc...@googlegroups.com
Eugene Pliskin created an issue
 
Jenkins / Bug JENKINS-59181
The plain HTTP request was sent to HTTPS port
Issue Type: Bug Bug
Assignee: Unassigned
Components: core
Created: 2019-09-02 10:59
Priority: Minor Minor
Reporter: Eugene Pliskin

Our Jenkins server is located behind nginx server which forwards external HTTPS requests to Jenkins server by HTTP. Generally I can access Jenkins by HTTPS from outside our corporate network. However there are some pitfalls, probably related to some invalid redirection commands inside Jenkins server which inadvertently change URL from HTTPS to HTTP.

For example:

  • open Jenkins web interface with HTTPS
  • open job configure page
  • press Save button

Then we get the following error message:

400 Bad Request

The plain HTTP request was sent to HTTPS port


nginx/1.16.1

This is because browser inadvertently switches from HTTPS to HTTP on Save button.

 

Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

eugene.pliskin@gmail.com (JIRA)

unread,
Sep 2, 2019, 7:07:04 AM9/2/19
to jenkinsc...@googlegroups.com
Eugene Pliskin updated an issue
Change By: Eugene Pliskin
Our Jenkins server is located behind nginx server which forwards external HTTPS requests from HTTPS port 10443 to Jenkins server by HTTP port 8090 . Generally I can access Jenkins by HTTPS from outside our corporate network. However there are some pitfalls, probably related to some invalid redirection commands inside Jenkins server which inadvertently change browser URL scheme from HTTPS to HTTP.

For example:
* open Jenkins web interface
with at HTTPS port 10443
* open job configure page
* press Save button


Then we get the following error message:
h1. 400 Bad Request


The plain HTTP request was sent to HTTPS port
----

nginx/1.16.1

This is because browser inadvertently switches from HTTPS to HTTP on Save button.

 

dbeck@cloudbees.com (JIRA)

unread,
Sep 4, 2019, 9:12:02 AM9/4/19
to jenkinsc...@googlegroups.com
Daniel Beck closed an issue as Cannot Reproduce
 

Almost certainly a bad reverse proxy configuration, https://wiki.jenkins.io/display/JENKINS/Running+Jenkins+behind+Nginx explains how to do it.

Change By: Daniel Beck
Status: Open Closed
Resolution: Cannot Reproduce
Reply all
Reply to author
Forward
0 new messages