Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

/saveUserKeys/ returns 404 on non-root TC server paths #49

Open
qmg-aki opened this issue Apr 12, 2019 · 1 comment
Open

/saveUserKeys/ returns 404 on non-root TC server paths #49

qmg-aki opened this issue Apr 12, 2019 · 1 comment
Assignees
@artem-fedorov

Comments

@qmg-aki
Copy link

qmg-aki commented Apr 12, 2019

I have a TeamCity server with a non-root path such as https://ci.root.com/teamcity/. Setting up the Blazemeter plugin with such a server causes /saveUserKeys/ to return 404.

Expected Behavior

On setting up the TC Blazemeter plugin according to the guide, Blazemeter gets set up successfully.

Current Behavior

On setting up the TC Blazemeter plugin according to the guide with my API key ID and secret as well as the URL set to https://a.blazemeter.com , on clicking Save, I get the following error on TeamCity:

Error: Invalid XML: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>404 Not Found</title> </head><body> <h1>Not Found</h1> <p>The requested URL /saveUserKeys/ was not found on this server.</p> </body></html>

Possible Solution

The issue seems to be related to BlazeRunTypeController#register. Registering the controller of /saveUserKeys/ does not seem to take into account the non-root path. So instead of registering something like https://ci.root.com/teamcity/saveUserKeys/ it is registering https://ci.root.com/saveUserKeys/.

Steps to Reproduce

  1. Setup a TC server with a non-root path such as https://ci.root.com/teamcity/
  2. Install Blazemeter TC plugin
  3. Configure the plugin with a valid API key ID, secret and the URL
  4. Click Save
@artem-fedorov artem-fedorov self-assigned this Apr 12, 2019
@artem-fedorov
Copy link

Thank you @qmg-aki
Will look at this issue

@artem-fedorov artem-fedorov mentioned this issue May 20, 2019
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@artem-fedorov artem-fedorov

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@qmg-aki @artem-fedorov