Bug 40006

Summary: Upgrading install.pl shows code vs HTML
Product: Koha Reporter: Shane Sammons <ssammons>
Component: Installation and upgrade (web-based installer)Assignee: Bugs List <koha-bugs>
Status: NEW --- QA Contact: Testopia <testopia>
Severity: minor    
Priority: P5 - low CC: dcook, gmcharlt, jonathan.druart
Version: 25.05   
Hardware: All   
OS: All   
GIT URL: Change sponsored?: ---
Patch complexity: --- Documentation contact:
Documentation submission: Text to go in the release notes:
Version(s) released in:
Circulation function:
Attachments: Screen segment of Chrome browser showing code vs HTML output
Revised screen showing its the browser NOT source code
Images of Chrome's View Source

Description Shane Sammons 2025-05-27 19:22:25 UTC
Created attachment 182806 [details]
Screen segment of Chrome browser showing code vs HTML output

When upgrading from version 23 (sorry I did it by accident, so I didn't not the subversion) after entering the credentials from the .xml file and proceeding to update the database, install.pl shows code above the HTML code, and I believe this breaks the HTML structure, viewing the page source it looked the same as the page, less in Chrome it puts line numbers on the left.

Here is what appears about the HTML tags.
0E0
Status: 200 OK
Set-Cookie: CGISESSID=af07240f027e658abfa81c3155df289f; path=/; HttpOnly; SameSite=Lax
Date: Tue, 27 May 2025 19:03:47 GMT
Cache-control: no-cache
Content-script-type: text/javascript
Content-style-type: text/css
Pragma: no-cache
X-frame-options: SAMEORIGIN
Content-Type: text/html; charset=UTF-8
Comment 1 Jonathan Druart 2025-05-28 09:40:26 UTC
Looks ok for me.
Comment 2 Shane Sammons 2025-05-28 12:04:57 UTC
Created attachment 182814 [details]
Revised screen showing its the browser NOT source code

This is what I saw in the browser, it is code, not rendered HTML
Comment 3 Shane Sammons 2025-05-28 12:06:10 UTC
Created attachment 182815 [details]
Images of Chrome's View Source

Here it is rendered the exact same way with view source as the HTML page.
Comment 4 David Cook 2025-05-29 01:56:07 UTC
Hmm that's interesting. That suggests that two sets of HTTP headers were generated...  with a 0E0 in between them it seems...

It sounds like you have an atypical installation if you're getting to this screen. If you're not able to run the database update, you could just rollback the code anyway.