Jump to content


  • Posts

  • Joined

  • Last visited

Profile Information

  • Gender
    Not Telling

Darghon's Achievements


Member (2/5)




Community Answers

  1. Hi all, I've currently been using a cookie as a "remind me" value for keeping users logged in for an entire day. Now, after googling about cookie security it all comes down to the same underlying statements. Cookies are not secure, and any data it contains is by extension, also not secure. Now, due to the fact that I need the "remind me" functionality, I was wondering what the best practice for this is. All my users have a UUID assigned to them, which is a 36-char long random string (in a specific pattern). At the moment, I store that UUID in the cookie, and if the system finds it, it checks if the user exists, and re-assigns the session if it expired, within the valid period of the cookie. Now, what should I do to make this better? Any suggestions are welcome. Thanks
  2. Well, since no one was able to help me, and I've eventually managed to fix this, I'll add my solution (and problems) in this post. So, I needed to connect to a Soap Service using WSSE. Not with a user/pass auth in it, but with a client certificate, a binary security token and such wonderful things. First, I needed to make a p12 certificate file, using my client certificate (with the cert chain) and my private key (used to request the client certificate). Next, I needed to convert the p12 file to a BASE64 encoded pem file. Finally, in the soap_client constructor, you need to add "local_cert" and "passphrase" in the options part with the full path of the pem file, and your used password (if any). Next, and this one was my biggest issue, make sure your server can resolve the host address of the webservice. Ping it first, and if needed, add it to your host file *facepalm* Finally, construct your soap envelop (I've used a public PHP WSSE library for mine), and execute the request. Feel free to ask more details if need be.
  3. The above is still an issue, anyone?
  4. Hi all, I've been struggling for months with a connection to a DataPower webservice using PHP. In SoapUI I've managed to get a response (an error message, but a response non the less) but in php, Soap always returns a NULL value. The service in question requires me to use a client certificate. Creating a p12 keystore with my private key (used to request the certificate) and the complete certificate chain provided by the service host, I'm able to get a connection using SoapUI (by using ssl for each request with the formentioned p12 file) Now, I want to accomplisch the same thing in php, so, I did the following: - I installed the root and CA2 certificate from the service provider on my php server - I construct a soap_client using the received wsdl file (same one as I use in SoapUi) and add the below listed options to the constructor $options = [ 'trace' => 1, 'exceptions' => 1, 'local_cert' => $this->_getCertificateLocation('P12_KEYFILE'), 'passphrase' => $keyfile_passphrase ]; The _getCertificateLocation returns the absolute path of the cert file, which is correct and accessable. Alternatively I've also tried to convert the P12 file to a PEM file using the below command, but results in thee same effect. openssl pkcs12 -in discimus_keystore.p12 -out discimus.pem -clcerts Anything I need to add/reconsider? or any advice on this matter? Thanks for any help. Darghon
  5. well, in my opinion I don't think that doing the clearfix in that way is the best way of doing it, at least not if you work with a lot of floats. I personally have the reflex of grouping divs together, so allowing me to add a clearfix class is a lot faster then adding extra id's or classes to the clearfix layout. I will add the IE7 trigger to my code, and thx for your input about my question, I've spent the entire weekend trying to get it working, but with no luck. liquid designs are still out of my reach, or at least the vertical liquid is... cheers all
  6. Wow, nice code, but I've been tinkering with it, and unfortunately I have the following problems with it the body overflow:hidden will cut any content that exceeds the page length, => this one makes the script unusable so, I removed the overflow, removed the padding and margin of 32k or so added a height:100% to html, body and container, and the menu and content 99%, so now the page is filled, without a scroll bar but if the content is larger, the content div stretches, but the menu doesn't (stays the page size without scrollbar). I don't really think it's possible to solve that one, but is it possible to add a header above the menu and content, and let the menu and content stretch to the bottom of the page? the 99% now creates a scroll bar, because a header was added. any fixes for this? or fixes for any of the other problems? Css: html{ height:100%; } body { font-size:76%; font-family: verdana, arial, sans-serif; background: #f0f0f0; word-wrap:break-word; height:100%; padding:0px; margin:0px; } #container { overflow:auto; background:#333; height:100%; } .header { width:100%; padding:10; margin:0; text-align:center; font-size:300%; } .menu { float:left; width:280px; padding:5px; color:#FFFFCC; background: #0099CC; } .content { margin-left:300px; padding:5px; background:#CCCCCC } .menu, .content { height:99%; } h1 { font-size:150%; margin:0; padding:10px 0; color:#fff; } h3 { font-size:130%; margin:0; padding:8px 0; } p { font-size:1em; line-height:1.5em; margin:0; padding:5px 0; } .clearfix:after { content: "."; display: block; clear: both; visibility: hidden; line-height: 0; height: 0; } .clearfix { display: inline-block; } html[xmlns] .clearfix { display: block; } * html .clearfix { height: 1%; } Html: <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en"> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> <title>Fixed left flexible right equal-height 2 columns</title> <LINK REL="StyleSheet" HREF="test.css" TYPE="text/css" MEDIA=screen> <!--[if lte IE 7]> <style type="text/css"> body {word-wrap:break-word;} .content {display:inline; float:left; margin-left:0; margin-right:0;} #container {display:inline-block;} </style> <![endif]--> </head> <body> <div id="container"> <div class="header">Header is here</div> <div class="menu"> <h3>Left 300px</h3> <ul> <li>option 1</li> <li>option 2</li> </ul> </div> <div class="content"> <h3>Remainder in %</h3> <h3>The site content comes here and needs to fill the screen</h3> <p>No fauex column image. Background colors give equal height impression. Layout concept is originally from a Stu Nicholes idea.</p> <p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Mauris ut ultrices sapien. Etiam aliquet ligula sed urna lobortis mattis. Aliquam eu nibh eget diam hendrerit pellentesque. Proin ac risus metus. Curabitur ipsum ligula, bibendum ac rhoncus ut, mollis quis dolor. Proin lorem est, venenatis nec pellentesque eget, dignissim vitae nisi. Pellentesque ornare dignissim tempor. Sed elit sapien, pellentesque quis accumsan eget, vestibulum a sapien. Aliquam at consectetur odio. Proin ut velit nec nunc commodo iaculis sit amet eget lacus. Donec condimentum mollis lacus non interdum. Vestibulum at lectus lorem.</p> <p>"At vero eos et accusamus et iusto odio dignissimos ducimus qui blanditiis praesentium voluptatum deleniti atque corrupti quos dolores et quas molestias excepturi sint occaecati cupiditate non provident, similique sunt in culpa qui officia deserunt mollitia animi, id est laborum et dolorum fuga. Et harum quidem rerum facilis est et expedita distinctio. Nam libero tempore, cum soluta nobis est eligendi optio cumque nihil impedit quo minus id quod maxime placeat facere possimus, omnis voluptas assumenda est, omnis dolor repellendus. Temporibus autem quibusdam et aut officiis debitis aut rerum necessitatibus saepe eveniet ut et voluptates repudiandae sint et molestiae non recusandae. Itaque earum rerum hic tenetur a sapiente delectus, ut aut reiciendis voluptatibus maiores alias consequatur aut perferendis doloribus asperiores repellat."</p> </div> </div> </body> </html>
  7. Thx for the reply but that doesn't really solve my problem. I have a reset.css stylesheet attached first, so all paddings and margins and such are all set to 0 I realise that the position absolute wasn't really needed, but I wanted to make sure that the container div stretched over the entire page. now my question was, how can I make sure that the content div will allways take the remaining space next to the menu, so that the menu always stays the same, but that the content changes with screen resolutions. but the content always needs to be the max width possible, so setting a min-width, max-width won't help me.
  8. there are 2 ways to fix it first you can just decrease your div height with the padding you want (so instead of 49px, 34px) the 2nd way is the best way: set a margin-top on your input, this will fix the problem without resizing the div
  9. Hi, I'm attempting a liquid layout and am encountering problems I can't seem to find a fix for I have 2 boxes next to eachother, the first box has a fixed size, and the 2nd should stretch to fully cover the page. style: body{ width:100%; height:100%; } .container{ width:100%; height:100%; display:block; position:absolute; top:0; left:0; } .menu{ width:300px; height:100%; margin:5px; padding:5px; float:left; } .content{ height:100%; width:100%; float:left; padding:5px; margin:5px; } html: <html> <head></head> <body> <div class="container"> <div class="menu"> <ul> <li>option 1</li> <li>option 2</li> </ul> </div> <div class="content"> <p>The site content comes here and needs to fill the screen</p> </div> </div> </body> </html> the html code has been simplified, but should make the intention clear. the 2nd div is placed under the menu (because of the 100% width) how can I make sure that the 2nd div (content) is fully stretched, next to the menu, and most importantly, in every webbrowser.
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.