playframework / playframework/play1

Same File Have different ETag on from different server response with Play 1.2.10,

Open
#1,202 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Java
Stars
1.6k
Forks
671
Avg merge
12d 15h
Merged PRs (30d)
1

Description

Hi Team,
I am working on old play 1.2.10 application , where we use activator start/run to launch the web application. I have load balance server as apache and two server instance of application. I want to generate same ETag from both server. Cloud you please help me , where I can find and fix this. I am new to play and we are using java controller.
I tried to disable using below conf parameter in application.conf, but does not works

Disable the Etag Creation By Play Server

http.useETag=false
I need help to over-ride the Assets functionality using java.

Assets built in Note :Etag support
The Assets controller automatically manages ETag HTTP Headers. The ETag value is generated from the digest (if sbt-digest is being used in the asset pipeline) or otherwise the resource name and the file’s last modification date. If the resource file is embedded into a file, the JAR file’s last modification date is used.

When a web browser makes a request specifying this Etag then the server can respond with 304 NotModified.

Thank you in Advance.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with application.conf and the Assets controller behavior described in the issue, then trace how activator start/run serves assets in Play 1.2.10. Check the Java controller entry point and the http.useETag setting. Done means determining why the two application servers produce different ETags and documenting or implementing a supported way to make their responses consistent.

Written by the indexing model from the issue text.

Assessment

Tech stack
apache, java
Domain
backend, web-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.