tag:service.skybound.ca,2010-06-18:/discussions/problems/121934-stylizer-6-and-css-pathsStylizer: Discussion 2015-01-03T13:37:18Ztag:service.skybound.ca,2010-06-18:Comment/355862202014-12-19T12:03:18Z2014-12-19T12:03:18ZStylizer 6 and CSS paths<div><p>Hi Villle,</p>
<p>I don't think the port number is the problem. The port number
only determines how the connection to the server is made; it's not
a part of the actual HTTP request, so I don't see how it could lead
to a "400 Bad Request" error.</p>
<p>It's possible that your server is expecting a certain HTTP
header that Stylizer does not include in the request, or that one
of the headers Stylizer provides is not in a format the server
expects.</p>
<p>Would you be able to install <a href=
"http://www.telerik.com/fiddler">Fiddler</a>? It is a free HTTP
traffic monitor, and it will allow you to compare the raw HTTP
request sent by the browser to the HTTP request sent by Stylizer to
help us narrow down the problem.</p></div>Andrewtag:service.skybound.ca,2010-06-18:Comment/355862202014-12-21T08:01:23Z2014-12-21T08:01:23ZStylizer 6 and CSS paths<div><p>Hi Andrew,</p>
<p>I had Charles already installed so I used it, and it did give
some further clue: "Bad cookie header". Since the application I'm
looking at is running on Hapi, the problem is apparently with the
strict demands on RFC 6265 compliance; see <a href=
"https://github.com/hapijs/hapi/issues/1329">https://github.com/hapijs/hapi/issues/1329</a>
and <a href=
"http://www.hapijs.com/api/7.5.0#hapiserver">http://www.hapijs.com/api/7.5.0#hapiserver</a>
('strictHeader'). I haven't had the time yet to figure out how I
can turn the requirement off; the initial attempt to issue:</p>
<p>server.state('session', {<br>
strictHeader: false });</p>
<p>didn't help. I'll investigate more tomorrow. Would it be
possible to bring Stylizer's cookie handling to RFC compliance?</p></div>Ville Walverantatag:service.skybound.ca,2010-06-18:Comment/355862202014-12-22T01:07:36Z2014-12-22T01:07:36ZStylizer 6 and CSS paths<div><p>When Stylizer requests a CSS file, it simply obtains the cookie
that the browser used passes it through unaltered. I'm not sure
what more we could do to make it "RFC compliant" or why the browser
would be providing a different cookie than it uses itself.</p>
<p>Would it be possible to post a copy of the raw HTTP requests as
sent by the standalone browser, and as sent by Stylizer, for the
same CSS file?</p></div>Andrew