Openbravo Issue Tracking System - Retail Modules
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0047795Retail ModulesWeb POSpublic2021-10-01 12:392021-10-01 13:15
Reportercberner 
Assigned ToRetail 
PrioritynormalSeverityminorReproducibilityhave not tried
StatusclosedResolutioninvalid 
PlatformOS5OS Version
Product Version 
Target VersionFixed in Version 
Merge Request Status
Review Assigned Tocberner
OBNetwork customer
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0047795: Application Cache fails to load when using direct IP instead of localhost because of manifest
DescriptionApplication Cache for WebPOS fails to load correctly, if using a direct IP instead of localhost. It seems to be due to manifest, but I couldn't find the exact reason.

This results is the webpos not working in offline mode.

The issue is reproducible both in Chrome and Safari.
Steps To Reproduce1. Start tomcat with retail environment locally
2. Go to your IP:8080/openbravo/web/org.openbravo.retail.posterminal/?terminal=VBS-1
3. Try to login, the Application Cache error will appear

A screenshot shows the error, and you can see the IP in the top bar, which is not localhost.(Using localhost works fine)
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
related to defect 0047416 closed Retail Problem to access from iPad to WebPOS when tomcat is stopped 
Attached Filespng Screenshot from 2021-10-01 12-38-23.png (302,693) 2021-10-01 12:39
https://issues.openbravo.com/file_download.php?file_id=16238&type=bug
Issue History
Date ModifiedUsernameFieldChange
2021-10-01 12:39cbernerNew Issue
2021-10-01 12:39cbernerAssigned To => Retail
2021-10-01 12:39cbernerFile Added: Screenshot from 2021-10-01 12-38-23.png
2021-10-01 12:39cbernerTriggers an Emergency Pack => No
2021-10-01 12:52cbernerRelationship addedrelated to 0047416
2021-10-01 12:52cbernerDescription Updatedbug_revision_view_page.php?rev_id=23125#r23125
2021-10-01 12:56PracticsIssue Monitored: Practics
2021-10-01 13:14cbernerNote Added: 0132098
2021-10-01 13:14cbernerStatusnew => scheduled
2021-10-01 13:14cbernerStatusscheduled => resolved
2021-10-01 13:14cbernerResolutionopen => fixed
2021-10-01 13:15cbernerReview Assigned To => cberner
2021-10-01 13:15cbernerStatusresolved => closed
2021-10-01 13:15cbernerResolutionfixed => invalid

Notes
(0132098)
cberner   
2021-10-01 13:14   
It is not an issue, service workers don't work on a non-secure http connection, only over https. We will try to reproduce it using secured connection, and if so, the issue will be reopened and updated with the information necessary.