git.net

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[users@httpd] Issue with REST API payload response


Hi everyone!

 

We have a Java application deployed to a WebLogic application server as well as a separate Sencha ExtJS based application deployed directly to the document root of our Apache server. Apache is configured to reverse proxy the requests to the backend Java application and the Sencha application is configured to make REST API calls to the backend Java application via the proxy URL. So our URLs look something like:

 

Web URL for Java app: https://example.com/javaapp --> this is reverse proxying to WebLogic

Web URL for Sencha app: https://example.com/senchaapp --> this is just a folder called 'senchaapp' under Apache's document root, inside 'senchaapp' folder we are making REST calls to https://example.com/javaapp

 

We are seeing some strange behavior where certain REST API calls fail when accessing the Sencha application through Apache. We have tried deploying the Sencha application to the Java application itself (by adding the same folder which sits in the document root of the web server to the root of the WAR file) and the REST API calls are working as expected when we access it through the application server URL which leads us to believe there is an issue with our Apache configuration somewhere.

 

This is the behavior we are expecting:

  • Login to the Sencha application
  • Dashboard loads
  • Reload the page
  • Login again
  • Dashboard loads

 

This is the behavior we are seeing:

  • Login to the Sencha application
  • Dashboard loads
  • Reload the page
  • Login again
  • Spinning page

 

From developer tools in Firefox, the request that is failing is a REST API call that returns an unexpected payload response (even though status code is 200 for the request):

layName":"10 Character"},{"code":"C9","displayName"HTTP/1.1 200 OKCache-Control: no-store, no-cache, must-revalidate, max-age=0, post-check=0, pre-check=0, private

Date: Thu, 20 Sep 2018 23:00:43 GMT

Pragma: no-cache

Content-Length: 324

Content-Type: application/json

Expires: Tue, 03 Jul 2001 06:00:00 GMT

Last-Modified: Thu, 20 Sep 2018 23:00:43 GMT

X-V3-APP: xxxxxxxx-xxxx-xxxx-xxxx

X-FRAME-OPTIONS: SAMEORIGIN

Strict-Transport-Security: max-age=31536000; includeSubDomains

X-WebKit-CSP: script-src 'self' 'unsafe-inline' 'unsafe-eval'; options inline-script eval-script; xhr-src 'self'; form-action 'self'; connect-src 'self'; reflected-xss block

Content-Security-Policy: script-src 'self' 'unsafe-inline' 'unsafe-eval'; options inline-script eval-script; xhr-src 'self'; form-action 'self'; connect-src 'self'; reflected-xss block

X-XSS-Protection: 1

X-Content-Security-Policy: script-src 'self' 'unsafe-inline' 'unsafe-eval'; options inline-script eval-script; xhr-src 'self'; form-action 'self'; connect-src 'self'; reflected-xss block

{"items":[{"internalName":"xxxxxxxxxxxxxx","seqNo":1,"analyticsConfig":{"trackingName":"xxxxxxxxxx","variables":{"page_l4":"landing","page_l2":"mobile app","page_l3":"xxxxx","page_l1":"xxxxx"}},"name":"Home","icon":{},"subDashboard":false,"id":"xxxx","widgetLayout":"GR"}],"totalRecordsCount":1}

 

When we really are only expecting the payload response to return that last part:

{"items":[{"internalName":"xxxxxxxxxxxxxx","seqNo":1,"analyticsConfig":{"trackingName":"xxxxxxxxxx","variables":{"page_l4":"landing","page_l2":"mobile app","page_l3":"xxxxx","page_l1":"xxxxx"}},"name":"Home","icon":{},"subDashboard":false,"id":"xxxx","widgetLayout":"GR"}],"totalRecordsCount":1}

 

Has anyone ever seen this before and knows what is causing it?  I have attached our httpd.conf file for reference.

 

Any help would be greatly appreciated!

 

Thanks,

Christina


This e-mail message and any files transmitted with it may contain confidential and proprietary information and are intended solely for the use of the individual or entity to which they are addressed. Any unauthorized review, use, disclosure or distribution is strictly prohibited. If you have received this e-mail in error please notify the sender by reply email and destroy all copies of the original message. Thank you for your cooperation.

Attachment: httpd.conf
Description: httpd.conf

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx