New issue
Advanced search Search tips

Issue 608495 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: May 2016
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

OmahaProxy Blink Change Log feature broken

Reported by msimprov...@gmail.com, May 2 2016

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.29 Safari/537.36

Steps to reproduce the problem:
1. Navigate to omahaproxy.appspot.com
2. Scroll down and enter an old version and a new version.
3. Click the "Show Change Log" button. It works.
4. Now check "Blink Change Log" and then click the "Show Change Log" button. It's broken.

What is the expected behavior?
Both the regular Change Log and the Blink Change Log modes should provide a link to view the change log.

What went wrong?
The Blink Change Log displays the following error message in bold red text:

<html><head> <meta http-equiv="content-type" content="text/html;charset=utf-8"> <title>500 Server Error</title> </head> <body text=#000000 bgcolor=#ffffff> <h1>Error: Server Error</h1> <h2>The server encountered an error and could not complete your request.<p>Please try again in 30 seconds.</h2> <h2></h2> </body></html>

Even once the root issue has been fixed, if this ever occurs again, the clean error message that the developer was clearly attempting to display should be displayed without all the underlying HTML code.

Did this work before? Yes This issue has been around for quite some time. However, the Blink Change Log did work properly a while ago.

Chrome version: 51.0.2704.29  Channel: beta
OS Version: 6.3
Flash Version: Shockwave Flash 21.0 r0

This is probably an infrastructure issue. The HTML issue should be easy to fix but maybe not the server issue.
 
Status: WontFix (was: Unconfirmed)
msimprovertechnologies@ ; Thanks for the issue, this is an intended behavior and changed from M47/M48(not sure exactly).You can get the Blink Roll inside the Change Log itself.

Hence closing the issue.
Can the feature be removed from the HTML code then?

Sign in to add a comment