Static resources are being rendered from the wrong place (on custom server)

[DvirSh]

I'm getting weird (and in my opinion wrong) behavior with static resources when I use custom server (on 2.0.0 Beta).
For example, if my custom server directs a request to "/blog/:id", then the static resources are being looked up in "./blog/static/image.jpg".

For easy reproduction, I've edited the render method of "blog" in "parameterized-routing":

return <div>
      <h1>My {this.props.id} blog post</h1>
      <p>
        Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod
        tempor incididunt ut labore et dolore magna aliqua.
      </p>
      <img src="./static/x.jpg" />
    </div>

And ofcourse added an image named "x.jpg" to "static" folder.

I can work it around by looking the file in "../static/x.jpg", but this is wrong since it exploits the fact that blog does not sit under index.js.

[arunoda]

@DvirSh could you send us a sample repo.
So, we could have a look at this closer.

[nkzawa]

Shouldn't it be <img src="/static/x.jpg" /> (no ./) ?
I assumed the page is served on /blog/id.

[DvirSh]

@nkzawa your'e right!